Event timing
Horary Ruling Planets, Two Definitions (F185)
get_horary_ruling_planets_variants
The two stated definitions of a number chart's ruling planets side by side, each with its 'system', 'source', 'alsoAt', 'disputedBy' and 'methodologyNote', never folded together. [KP] 'ksk-moment-ascendant': the day lord, the Moon's sign and star lords, and the sign and star lords of the Ascendant RISING at the moment of judgement (Reader 6 canon pp.210-212: number 100 casts Leo while 'the lagna is Dhanus'); 'readByKpJudgement' true, the set 'chart.rulingPlanets' and every KP judgement on a horary chart read. [KP-extended] 'prabhakar-number-ascendant' (New Dimensions of K.P. Astrology, c.2006): the number's sign and star lords stand in for the Ascendant's; reported, never applied. Each variant carries its 'ascendant' and 'rulingPlanets', and with query_event its 'fruitfulSignificators' for the event (null without one). Returns '{ questionNumber, applied, appliedBecause, variants[2], difference: { onlyUnderKsk, onlyUnderPrabhakar, sameSet, sameRanked, fruitfulSetMoves }, readers, note }'; 'readers' lists every tool that reads a horary chart's ruling planets and which definition it reads. Name which one you cite. The same block 'get_horary_chart_v2', 'get_horary_validation_panel', 'get_horary_number_intuition', 'get_horary_natal_crosscheck', 'get_medical_horary', 'get_career_horary' and 'get_arrival_timing' return as 'rulingPlanetsVariants'; given the same moment of judgement, each casts the same chart. The last three read no event, so call this without query_event, with their judgement_* fields, to match them. The chart is cast at the moment and place the question is judged: send 'judgement_datetime' (the local wall clock there), 'judgement_latitude', 'judgement_longitude', and 'judgement_utc_offset_minutes' or 'judgement_time_zone'. This tool needs no birth data. The result echoes 'horaryMoment' ('instant', 'local', 'place', 'source', 'utcOffsetSource') and 'deprecatedInput', which names any old field name the call used and the field to send instead.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| ayanamsa | enum: kp | kp_new | lahiri | raman | true_chitra | khullar | No | Ayanamsa system. Defaults to kp. |
| birth_datetime | string | No | Deprecated, use judgement_datetime. For this one release, a call with no judgement_* field is cast at this date and time and the place below, and the result's deprecatedInput says so. |
| latitude | number | No | Deprecated, use judgement_latitude. |
| longitude | number | No | Deprecated, use judgement_longitude. |
| utc_offset_minutes | number | No | Deprecated, use judgement_utc_offset_minutes or judgement_time_zone. |
| time_zone | string | No | Deprecated, use judgement_time_zone. |
| judgement_datetime | string | No | The moment the question is judged, as the local wall clock at the place of judgement, ISO 8601 with no zone suffix (e.g. 2026-10-20T10:30:00). Send it on every call; the result's horaryMoment echoes it. |
| judgement_latitude | number | No | Latitude of the place where the question is judged, north positive. |
| judgement_longitude | number | No | Longitude of the place where the question is judged, east positive. |
| judgement_utc_offset_minutes | number | No | UTC offset in force at the place of judgement at that moment, in minutes east of UTC (e.g. 330 for India, -240 for New York in summer). Prefer judgement_time_zone, which works it out; if both are given they must agree. |
| judgement_time_zone | string | No | IANA time zone of the place of judgement (e.g. "Asia/Colombo", "America/New_York"). The offset in force there at judgement_datetime is read from the tz database, daylight saving and past changes included. |
| target_number | number | Yes | KP horary question number (1-249) |
| query_event | string | No | Event being queried (e.g., 'Marriage', 'Career / Job Start'). Adds each set's fruitful significators for it. |
| query_datetime | string | No | Deprecated, use judgement_datetime. |
| query_latitude | number | No | Deprecated, use judgement_latitude. |
| query_longitude | number | No | Deprecated, use judgement_longitude. |
| query_utc_offset_minutes | number | No | Deprecated, use judgement_utc_offset_minutes or judgement_time_zone. |
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": "get_horary_ruling_planets_variants",
"arguments": {
"judgement_datetime": "2026-10-20T10:30:00",
"judgement_latitude": 6.927,
"judgement_longitude": 79.861,
"judgement_time_zone": "Asia/Colombo",
"target_number": 137
}
}
}