Advanced techniques

Bayesian Event Probability Score

get_event_probability

[Lumin extension, not a KP verdict] A per-planet 0-1 activation INDEX from explainable feature weights: matrix level (L1=1.0, L2=0.7, L3=0.5, L4=0.3), Ruling Planet presence (+0.30), active dasha layers (+0.25 each), natal retrograde (-0.20), denial-house overlap (up to -0.25), logistic-squashed. It is NOT a probability and the response's scoreProvenance says so: KP assigns no number to anything (Q012) and states there is no place for probabilities (KP-ABSOLUTES A7); every weight here is a Lumin convention. Returns ranked significators with per-feature contributions and a STRONG/MODERATE/WEAK/NEGLIGIBLE band that is not comparable with any other tool's band (F031). Use to ORDER candidates within one reading, never to state a likelihood; the promise verdict comes from analyze_natal_promise.

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 not provided.
house_group	array<house number (1-12)>	No	Override required houses.
denial_group	array<house number (1-12)>	No	Override denial houses.
as_of	string	No	ISO 8601 timestamp to evaluate (default: now).

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