Advanced techniques

Vitality / Constitutional Resilience Index (KP, 0-100)

get_vitality_index

Constitutional resilience and immunity score (0-100) with a recuperation class (FAST_HEALER/AVERAGE/SLOW_HEALER/FRAGILE). Components, each itemized in a factors array: the 1st CSL's 1-5-11 vs 6-8-12 significations (weighted L1=4..L4=1); the 1st CSL's STAR LORD on the same test, weighted higher (the real decider in KP) including its retrograde state; lagna lord placement; Sun (vital fire) and Moon (fluids/resistance) affliction via dusthana placement or Saturn/Mars/Rahu/Ketu conjunction within 8 degrees. Combustion (graded NONE/ORDINARY/FULL) and dignity are REPORTED in the factors and move no points: KP reads vitality from the 1st cusp sub lord's significations, and a planet's own dignity or combustion decides nothing (F066, Q023); a resistanceRatio from 1st-vs-6th house strength scores; and a penalty when the bhadhaka lord occupies or aspects the 1st house. Also returns susceptibilityBias (inferred weak areas). Supplementary lens, not medical diagnosis; no death prediction.

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