Advanced techniques

Qualitative Lifespan Band & Balarishta Lens (KP, no death dates)

get_longevity_balarishta

Qualitative lifespan-band estimation per KP Reader 3 ch.1 p.153 (Bhadhakasthana) and Reader 5 longevity transits. Returns: bhadhakasthana house (selected by lagna mobility, movable=11, fixed=9, dual=7 per KSK), maraka houses [2, 7, 12], 1st-CSL star lord signature, lifespanBand (SHORT / MIDDLE / LONG / INDETERMINATE), expectedAgeBand (qualitative band only, never an exact age), balarishtaWarning, and criticalWindows[] (dasha periods activating bhadhaka/maraka houses, ranked CAUTION / NOTABLE / PEAK_RISK with ageStart/End). BY DESIGN THIS TOOL DOES NOT AND CANNOT PREDICT DEATH DATES OR MOMENTS; outputs are qualitative bands and risk windows only. Restricted in some jurisdictions without consent; B2B advisor-tooling signal, never consumer-facing.

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.

Example call

Send the request as a standard MCP tools/call:

POST https://mcp.lumin.guru/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_longevity_balarishta",
    "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:

POST /v1/kp/longevity

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.