Event timing
Event Timing (v2)
find_event_timing_v2
Enhanced KP event timing: checks all 3 dasha levels (MD+AD+PD must jointly signify required houses), filters against Ruling Planets (fruitful significators only), integrates transit hierarchy for year/month/day narrowing. Use this instead of find_event_timing for precise, methodologically correct KP timing.
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 | Life event to find timing for. |
| house_group | array<house number (1-12)> | No | Override event lookup with explicit house numbers (1-12). When provided, event is ignored. |
| denial_group | array<house number (1-12)> | No | Houses that DENY the event (e.g., [1,5,9] deny marriage). Only used with house_group. If unsure, omit. The engine derives denial houses automatically from the event name. |
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": "find_event_timing_v2",
"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/event-timing/v2The 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.