Advanced techniques

Kalachakra Dasha, Raghavacharya reading (rows as antardashas) [Vedic Parashari]

get_kalachakra_raghavacharya_dasha

[Parashari, not KP] Kalachakra dasha in Raghavacharya's reading, where the nine-rasi pada rows are ANTARDASHA tables and the mahadashas are the KALACHAKRA NAVAMSAS of the nine padas counted forward from the Moon's, as Vimshottari counts nine nakshatras. The source is Raghavacharya's Kalachakramu (Telugu, 1930) through P.V.R. Narasimha Rao and Sanjay Rath. The Kalachakra navamsa is NOT the D9: each triad of nakshatras lays the twelve signs over its twelve padas, savya zodiacally from Aries, apsavya from Scorpio with Cancer and Leo inverted. Returns the nine mahadashas with the pada each comes from, the first running the unelapsed arc fraction of the Moon's pada, and each mahadasha's nine antardashas from its own pada's row read from the head (sub-sign years x mahadasha years / paramayu, summing to the mahadasha). Every row is its pada divided into nine consecutive Kalachakra navamsas, which is why the head is the start; the mahadasha's own sign need not be in the row at all (Aswini pada 2's Taurus is not). Gatis on every mahadasha change, read two ways as in get_kalachakra_dasha. Source class 'later': the primary is unseen here and the antardasha order and the balance are reconstructed and say so. Stops after the ninth mahadasha; nothing crosses on (mean stopping age 84.9 over 200 charts, 'lumin-engine/scripts/bp011-kalachakra-spread.ts'). Compare it with get_kalachakra_dasha through get_kalachakra_spread, which says which conclusions move between the readings on this chart. **'schedule.mahadashas' is paged**, in order and never cut inside a mahadasha, so each page carries the next mahadashas whole with their nine antardashas; 'balance', 'schedule.transitions' (the gatis), 'schedule.atBirth', 'schedule.atQuery' and the sources repeat on every page, so the running periods at 'query_date' read from page 1. Not a KP tool. No effect is emitted.

Parameters

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_kalachakra_raghavacharya_dasha",
    "arguments": {
      "birth_datetime": "1992-08-14T04:32:00",
      "latitude": 6.927,
      "longitude": 79.861,
      "utc_offset_minutes": 330,
      "ayanamsa": "kp"
    }
  }
}