Advanced techniques

Accident Risk Windows by Class (KP)

get_accident_window

KP accident-window detection. Identifies dasha periods with malefic activation (Mars / Saturn / Rahu) signifying risk houses, and classifies each window by accident class: VEHICULAR (3rd house), WORKPLACE (6+10), SURGICAL (1+8), ASSAULT (6+12), or GENERIC (4 or 8 with malefic). Severity bands: MINOR / MODERATE / SEVERE / LIFE_THREATENING. Returns ranked risk windows, aggregate type distribution, and the peak window. Books: KP Reader 6 case 50 and J5 p.50 worked accident case 23-7-1963. The Reader 3 citation this used to carry was wrong: it named ch.22, which is "Will stammering disappear?" (canon pp.310-313), and Reader 3 has no accident chapter. The house grammar (1st for the body, 4 and 8 supporting, 12 for confinement) is later KP practitioner literature, class modern, not KSK. Supplementary safety lens, not deterministic; flags caution windows, never predicts certain harm.

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.

Example call

Send the request as a standard MCP tools/call:

http

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_accident_window",
    "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.