Advanced techniques

Separation Risk Windows (KP T32)

get_separation_risk_windows

The risk calendar (T32): every MD-AD-PD period whose lords jointly signify any of 1/6/10, with the 2/7/11 houses they also touch, highest 'netRiskScore' first (the engine's own weighting on the 1/6/10 convention, labelled so in the citations, F006). Returns '{ peakRiskWindows: [{ fromDate, toDate, mahadasha, antardasha, pratyantardasha, separationHousesActive, marriageHousesActive, netRiskScore, rationale }], bookCitations, disclaimer, pagination, pageNote }'. **'peakRiskWindows' is paged.** The same list 'get_marital_separation' returns as 'peakRiskWindows'. Supplementary lens, not legal advice; a period of pressure, not a predetermined outcome.

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