Event timing
Ruling Planets at the Moment of Judgement
get_ruling_planets_at_judgement
The Ruling Planets of the moment the matter is judged ('judgement_datetime', default now, at the birth place unless a judgement place is given), which is the set KP times with (KP Reader 4 canon p.115: the planets ruling the moment the matter is judged). Same rule, variants and node rules as get_ruling_planets, which run at the birth moment give the set for RECTIFICATION. Returns '{ rpMoment, use, instant, local, place, datetimeDefaultedToNow, placeDefaultedToBirth, rulingPlanets: { weekdayLord, moonSignLord, moonStarLord, ascSignLord, ascStarLord, ranked[], variant, nodeRule, nodeAdjustments[], ... }, fruitfulFilterSet: { ranked[], nodeRule, note } }'. 'fruitfulFilterSet' is the set get_fruitful_significators and find_event_timing_v2 actually filter by at that moment, computed with no node substitution; it differs from 'rulingPlanets' only where the node rule moves a node. 'nodeRuleVariants' states all three node rules for the moment side by side, each with its methodology (what it does, source class, locus, how it differs): 'none' (the fruitful filter's, which no page states for selection, F166), 'books-substitute-when-alone' (Astrology for Beginners canon p.318, Astro Secrets canon p.512) and 'web-always-add' (KSK's own Reader 6 canon p.132, 'Rahu also should be taken as a ruling planet'); the caller's 'node_rule' is marked default. A node rule changes the list on 69.9% of skies (every 6 h through 2026, 'scripts/f166-node-rule-fruitful.ts'). 'holdsUntil' is the next instant one of the five members changes, solved and never a score: 'instant' in UTC, 'local' with the offset in force then only when 'judgement_time_zone' is sent, otherwise with the judgement's own offset (read 'utcOffsetSource'), 'changes' naming the member (the Ascendant's or the Moon's sign or star lord, or the day lord at the next sunrise at the place of judgement) with its old and new lord, 'rankedAfter', and each member's own next change in 'nextChangeByMember'. The set, and the fruitful set filtered by it, holds until that instant; say so when you quote it. The day lord runs sunrise to sunrise at the place of judgement.
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. |
| judgement_datetime | string | No | The moment the matter is judged, local wall clock at the birth place unless judgement_latitude/longitude are given (e.g. 2026-09-27T12:00:00). Defaults to now. |
| judgement_latitude | number | No | Latitude of the place of judgement. Defaults to the birth latitude. |
| judgement_longitude | number | No | Longitude of the place of judgement. Defaults to the birth longitude. |
| judgement_utc_offset_minutes | number | No | UTC offset of the place of judgement in minutes. Defaults to the birth offset when the place defaults to the birth place. |
| judgement_time_zone | string | No | IANA time zone of the place of judgement (e.g. "Asia/Colombo"), instead of judgement_utc_offset_minutes: the offset in force there at judgement_datetime is read from the tz database. If both are given they must agree. |
| rp_variant | enum: five-member-classic | seven-member-with-subs | No | Which RP list (default five-member-classic). seven-member-with-subs adds the Ascendant and Moon sub lords. |
| node_rule | enum: books-substitute-when-alone | web-always-add | none | No | How Rahu and Ketu join the RPs (default books-substitute-when-alone). |
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_ruling_planets_at_judgement",
"arguments": {
"birth_datetime": "1992-08-14T04:32:00",
"latitude": 6.927,
"longitude": 79.861,
"utc_offset_minutes": 330,
"ayanamsa": "kp"
}
}
}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.