Advanced techniques
Advanced Retrograde Analysis
get_retrograde_advanced
Advanced retrograde analysis: 3-state CSL interpretation (delayed/denied/sudden fulfillment based on star lord retrogression), retrograde dasha lord transit activation dates (Jupiter/Saturn crossing natal retro degree), and slow-planet station window mapping (suppression windows when retrograde over significator). Scan range up to 2 years.
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 | lahiri | raman | true_chitra | 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
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_retrograde_advanced",
"arguments": {
"birth_datetime": "1992-08-14T04:32:00",
"latitude": 6.927,
"longitude": 79.861,
"utc_offset_minutes": 330,
"ayanamsa": "kp"
}
}
}Engine endpoint
This tool delegates to the kp-engine endpoint:
POST /v1/kp/retrograde/advancedThe engine is a private internal service. All public access flows through the MCP server, which handles auth, rate limiting, and response compaction.
Birth data
This tool requires birth data. If you have already called set_birth_profile in the same conversation, the MCP server injects those fields automatically and you can omit them from the call.