Advanced techniques

KCIL Weighted Verdict (Khullar)

get_kcil_verdict

S.P. Khullar's three-authority KCIL weighted verdict — produces a 0-100 KCIL score per house cusp instead of KP's binary promise/denial. Star Lord (15% weight) proposes, Sub Lord (60%) disposes, Sub-Sub Lord (25%) delivers the end result. Returns per-cusp scores with full lord-level breakdown (housesSignified, supportingHits, denialHits) and an overall score with verdict thresholds (≥70 STRONG_PROMISE, 50-69 MIXED, 30-49 WEAK, <30 DENIED). Use as a continuous-scoring alternative to analyze_natal_promise when you want a graded readout. Accepts an event name OR custom (primary_houses + house_group + denial_group).

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 (e.g., "Marriage"). Required if primary_houses + house_group not provided.
house_group	array<house number (1-12)>	No	Override required houses (e.g., [2,7,11] for marriage).
denial_group	array<house number (1-12)>	No	Override denial houses (e.g., [1,6,10] for marriage).
primary_houses	array<house number (1-12)>	No	Override which cusps to score (default: derived from event's primary_house).

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