Advanced techniques
Disease Nature Decoder (6th CSL, KP)
get_disease_nature
Decodes the 6th cusp sub lord into the NATURE of disease, not merely its location (KP Reader 3 canon p.295 for the procedure, canon p.190 for chronicity, canon pp.292 and 296-297 for the keyword lists). Three layers: (a) planet-to-ailment-class keywords for the 6th CSL and separately for its star lord (e.g. Saturn = chronic/degenerative, Mars = acute inflammation/surgery, Ketu = viral/autoimmune/misdiagnosed); (b) chronicity from the modality of the sign the CSL occupies (movable = ACUTE self-limiting, fixed = CHRONIC long-standing, dual = RECURRING relapsing); (c) body part from the CSL's nakshatra position via the 27-fold Kalapurusha map, with the 12-sign body part as a secondary read. Severity gates from the CSL's own significations (8 = serious/prolonged, 12 = hospitalization tendency, 11 = curable) combine into a CURABLE / MANAGEABLE / PERSISTENT curability verdict. Natal-only, no dasha walk. Supplementary lens, not a medical diagnosis.
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:
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_disease_nature",
"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.