Advanced techniques
Retrograde Panel
get_retrograde_panel
Retrograde panel (renamed from get_retrograde_advanced on 2026-10-08), three blocks in one call: (1) 'retroCSLThreeState', the 3-state CSL interpretation (delayed/denied/sudden fulfilment by star lord retrogression); (2) 'retroDashaActivation', the dates transit Jupiter or Saturn crosses the natal degree of a running dasha lord that was retrograde at birth; (3) 'stationWindowMapping', the Jupiter and Saturn stations in the scan that fall near the event's significators. Scan range up to 5 years. Returns '{ retroCSLThreeState, retroDashaActivation, stationWindowMapping, summary, methodSeams[] }'. Each block is also a tool of its own, named in 'methodSeams': get_retrograde_csl_states, get_retrograde_dasha_activation, get_station_windows. **Read the CSL states from get_retrograde_csl_states, not from 'retroCSLThreeState'** (F165): this block's STATE_B_DENIAL is disputed in the corpus (failure at KP Reader 6 canon p.155, delay until the retrograde lord turns direct at Astro Secrets canon p.1379), and it keys on the cusp's star lord where the pages key on the sub lord's own. Since F160 it reads Rahu and Ketu as never retrograde, as KSK does (Reader 6 canon p.114); each entry's 'astronomical' carries the old reading (nodes always retrograde) and the state it gives, and 'astronomicalStateDiffers' names the cusps where they part. The keying ships unchanged and 'methodSeams' points at the tool that carries the corrected one. On a natal chart retrogression gates no promise (R2). The station windows are Sutra 32's release (Reader 6 canon p.155); the dasha-lord activation has no source found.
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. |
| event | event name | No | Event for retrograde analysis (default: Marriage). Ignored if house_group is provided. |
| scan_start_utc | string | No | Transit scan start (ISO 8601, default: now) |
| scan_end_utc | string | No | Transit scan end (ISO 8601, default: 1 year from start) |
| house_group | array<house number (1-12)> | No | Override event lookup with explicit house numbers (1-12). When provided, event is ignored. |
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_retrograde_panel",
"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.