Advanced techniques

Chronic Disease Watch-Decade Panel (KP, 8 conditions)

get_chronic_disease_panel

Multi-disease watch-decade panel scoring 8 chronic conditions: cardiac, diabetes, kidney, liver, neurological, mental-health, respiratory, skeletal. Each disease gets (a) a 0-100 signature strength from key planets afflicting 6/8/12 plus sign affinity on 6th cusp plus 6th-CSL match, (b) a severity classification (LOW/MODERATE/HIGH/CRITICAL), (c) watch-decade dasha bands (ONSET_RISK / AGGRAVATION / CRITICAL) drawn from MD+AD where the disease's key planets activate. Books: KP Reader 3 ch.19 "Disease", canon pp.291-301, plus canon p.190 for the chronicity rule. The per-disease house assignments are this engine's and are not in those pages. **Paged by disease**, each returned whole with its watch decades, signature hits and rationale, so a page is a complete condition rather than a partial one; 'topRiskDisease', 'topRiskDecade', 'bookCitations' and the disclaimer repeat on every page. Supplementary lens, not diagnostic; never a substitute for medical evaluation.

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