Advanced techniques

Multi-System Verdict Comparator

get_multi_system_verdict

Cross-SCHOOL verdict for an event, inside the KP lineage only. Runs orthodox KP CSL analysis, KCIL (Khullar weighted 15/60/25), 4-Step (Hariharan star-lord-of-sub-lord, corrected attribution per F037), and Bosmia 6-fold (filtered through 7-RP), and returns four normalised verdicts with a consensus band and an average score. **Every number it emits is a Lumin convention and the response says so in 'scoreProvenance'** (F031): averaging four schools presumes they measure one quantity from four angles, and they do not, they differ on which lord carries the authority. For the same comparison with no arithmetic at all, and reaching past the KP lineage to Parashari, Jaimini and Tajik, call 'get_paradigm_panel' instead.

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.
event	event name	No	Event name. Required if house_group + primary_houses not provided.
house_group	array<house number (1-12)>	No	Override required houses.
denial_group	array<house number (1-12)>	No	Override denial houses.
primary_houses	array<house number (1-12)>	No	Override which cusps to score.

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