Specialized analysis

Dosha Detection

check_doshas

Detect 5 classical chart afflictions (doshas). **Manglik** (Mars in 1/2/4/7/8/12, marriage friction), **Kalsarpa** (all 7 visible planets between Rahu and Ketu, for variant typing use 'get_kalsarpa_variants'), **Sadhesati** (7.5-yr Saturn transit, for phase breakdown use 'get_sade_sati_phases'), **Pitra Dosha** (paternal-lineage karma signature), **Kemadruma** (Moon isolation, no planets in 2nd/12th from Moon). Returns '{ doshas: [{ name, plainName, present, severity, details, plainMeaning, cancellations[], remedies[], provenance }] }'. **Read 'provenance' before repeating any of it.** Manglik, Sadhesati and Kemadruma are 'classical' with a locus; **Kalsarpa and Pitra Dosha are 'unsourced'** — no classical text and no page of the 5,045-page KP corpus contains either, so both report 'severity: 'Present'' with no grade, and their invented Severe/Moderate bands were removed (F054). 'plainMeaning' is the reader-facing sentence and assumes no Sanskrit.

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": "check_doshas",
    "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.