Advanced techniques

Treatment Modality Selector (KP)

get_treatment_modality

Answers 'which system of medicine will work?' by reading three cusp sub lords: the 6th CSL (nature of the cure agent), the 11th CSL (what delivers the cure), and the 12th CSL (hospital vs home). Each CSL's planet maps to modalities (Sun = allopathy/hospital, Moon = diet/counselling/homeopathy, Mars = surgery, Mercury = diagnostics-led/physiotherapy/mixed pathies, Jupiter = ayurveda/herbal, Venus = comfort/naturopathy, Saturn = long-term regimen/chronic care, Rahu = experimental/foreign/strong drugs, Ketu = faith healing/alternative medicine) and is scored 11th x3, 6th x2, 12th x1 with star lords at half weight. Extra verdicts: surgical route indicated (Mars on the 6/11 cure axis plus 8th CSL signifying 8), hospital vs home care, and doctor change (10th CSL signifying 6/8/12 at L1/L2). Optionally pass current_treatment for an ALIGNED / PARTIAL / MISALIGNED verdict against the ranking. Natal-only, no dasha walk. Supplementary lens, not treatment advice.

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.
current_treatment	enum: ALLOPATHY \| AYURVEDA \| HOMEOPATHY \| SURGERY \| …	No	The system of medicine currently being followed. Returns an alignment verdict comparing it against the chart's modality ranking.

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