Advanced techniques

Bayesian Event Probability Score

get_event_probability

Per-planet P(event fires) ∈ [0, 1] computed 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 to bounded probability. Returns ranked significators with per-feature contributions and an aggregate STRONG/MODERATE/WEAK/NEGLIGIBLE verdict. Use as a numerical sanity check on dasha-period predictions.

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	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
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"
    }
  }
}

Engine endpoint

This tool delegates to the kp-engine endpoint:

http

POST /v1/kp/event-probability

The 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.