Event timing
Timing by Ruling Planets, No Number or Chart (KP)
get_rp_timing
[KP] Timing by the ruling planets alone, with NO birth chart and NO horary number: KSK, Reader 6 canon p.211, 'ruling planets help us to give precise predictions regarding any question even in the absence of birth chart.' Takes only the moment and place the matter is judged: 'judgement_datetime' (the local wall clock there), 'judgement_latitude', 'judgement_longitude', and 'judgement_utc_offset_minutes' or 'judgement_time_zone'. Takes the Ruling Planets of that moment from the real sky, screens them for tempters (an RP in the star or sub of a retrograde planet; the three corpus forms are all reported, and Rahu and Ketu are never retrograde in KP), then moves four bodies forward and returns every stretch in which the body's sign lord, star lord and sub lord are all surviving ruling planets. Which body answers which question is canon p.140: the Ascendant for the same day (canon p.139, 'When this position in that sign would rise in the east'), the Moon for days within a month, the Sun beyond a month ('When Sun transits a position in the Zodiac ruled by the ruling planets, the event will fructify'), Jupiter for years. Read the mover whose horizon fits the matter; the tool does not choose it. Sun windows carry 'moonAgrees', the stretches in which the Moon's sign and star lords are ruling planets too (canon p.212's confirmation); Ascendant windows carry 'subSubCells'. No window is picked or scored: where two qualify KSK takes the stronger ruling planet's (canon p.212), and each window names the RP role its lords hold. Defaults follow KSK's two worked examples (canon pp.138, 211): the four-member RP list (day, Moon sign, Moon star, Lagna sign), no node rule, the Reader 6 screen. Checked against both: p.211's delivery comes out Scorpio, Jupiter star, Mars sub in mid-November 1969 (the page's 18th is a day after the engine's window, when the Moon confirms), and p.138's messenger at about 4 P.M. with the screen set aside (under the screen that sky's Sun is a tempter). Returns '{ judgement, rulingPlanets, retrogradeScreen, screenApplied, timingSet[], movers: [{ mover, horizon, windows: [{ from, to, fromLocal, toLocal, sign, signLord, starLord, subLord, roles, retrogradeAtWindow, moonAgrees?, subSubCells? }] }], rules, deprecatedInput, pagination, pageNote }'; 'judgement' carries 'instant', 'local', 'place', 'utcOffsetSource' ('given' or 'time-zone') and 'timeZone', and 'deprecatedInput' names any old field name the call used and the field to send instead. **Paged by mover.** For a question WITH a number, 'get_horary_chart_v2' stays KSK's primary method.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| judgement_datetime | string | Yes | The moment the matter is judged, as the LOCAL wall clock at the place (e.g. 2026-09-28T10:30:00). The only time the method needs: no birth time and no number. |
| 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. |
| 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. |
| ayanamsa | enum: kp | kp_new | lahiri | raman | … | No | Ayanamsa (default kp, KP Old). |
| movers | array<enum: lagna | moon | sun | jupiter> | No | Which bodies to move (default all four). Reader 6 canon p.140: lagna for the same day, moon for days within a month, sun beyond a month, jupiter for years. |
| rp_variant | enum: four-member-reader6 | five-member-classic | seven-member-with-subs | No | Which RP list (default four-member-reader6, the list of KSK's worked examples: day, Moon sign, Moon star, Lagna sign). |
| node_rule | enum: none | books-substitute-when-alone | web-always-add | No | How Rahu and Ketu join the RPs (default none, as in both worked examples). |
| screen | enum: reader6-star-or-sub | beginners-sub-only | ignore | No | Which retrograde screen builds the windows (default reader6-star-or-sub, KSK's on canon p.211). All three are reported whichever is applied. |
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_rp_timing",
"arguments": {
"judgement_datetime": "...",
"judgement_latitude": 6.927,
"judgement_longitude": 79.861,
"judgement_time_zone": "Asia/Colombo"
}
}
}