Advanced techniques
Rectify by Event Ruling Planets (KP T42)
rectify_by_event_ruling_planets
KP birth time rectification by event ruling planets (T42, renamed from get_rectification_advanced on 2026-10-08): for each candidate minute in the range, and each known life event (with date AND location), computes the Ruling Planets at that event moment and checks their overlap with the candidate chart's fruitful significators for the event, plus whether the candidate's dasha at the event date signifies its houses. Returns '{ originalTime, searchRange, knownEvents, minEventThreshold, confidence: STRONG | MODERATE | WEAK | INSUFFICIENT, confidenceRationale, candidates: [{ adjustmentMinutes, datetime, ascendantSign, ascendantDegree, rpScore, dashaScore, combinedScore, eventMatchCount, eventTotalCount, rpEventDetails, dashaDetails }], bestMatch, confidenceWindow, summary }'; **'candidates' is paged**. The scores are engine weightings; 'confidenceWindow' is the span of minutes that fit the events as well as the best one does.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| birth_datetime | string | Yes | Birth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00"). |
| latitude | number | Yes | Birth location latitude. Range: -90 to 90. |
| longitude | number | Yes | Birth location longitude. Range: -180 to 180. |
| utc_offset_minutes | number | Yes | UTC offset in minutes (e.g., 330 for IST, -300 for EST). |
| ayanamsa | enum: kp | kp_new | lahiri | raman | true_chitra | khullar | No | Ayanamsa system. Defaults to kp. |
| known_events | array<object> | Yes | Known life events with dates, houses, and locations |
| range_minutes | number | No | Search range in minutes (default: 30) |
| step_minutes | number | No | Step size in minutes (default: 2) |
Example call
Send the request as a standard MCP tools/call:
POST https://mcp.lumin.guru/mcp
Authorization: Bearer mcp_yourkey...
Accept: application/json, text/event-stream
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "rectify_by_event_ruling_planets",
"arguments": {
"birth_datetime": "1992-08-14T04:32:00",
"latitude": 6.927,
"longitude": 79.861,
"utc_offset_minutes": 330,
"ayanamsa": "kp",
"known_events": []
}
}
}Birth data
This tool requires birth data on every call. The MCP server is stateless, so calling set_birth_profile first validates the data and returns the reading plan, but it does not store anything. Repeat the same five fields here.