Chart and reference
Event Dasha Periods
get_event_dasha
Find which dasha periods activate a specific life event. Returns only periods where MD+AD lords signify the required houses, ranked by coverage.
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 | Yes | Event to analyze dasha periods for. |
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_event_dasha",
"arguments": {
"birth_datetime": "1992-08-14T04:32:00",
"latitude": 6.927,
"longitude": 79.861,
"utc_offset_minutes": 330,
"ayanamsa": "kp",
"event": "Marriage"
}
}
}Engine endpoint
This tool delegates to the kp-engine endpoint:
POST /v1/kp/smart-dasha/eventThe 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.