Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Misdiagnosis Risk Score (natal 6th-chain diagnostic-ambiguity flags)

get_misdiagnosis_risk

Deterministic diagnostic-ambiguity audit of the natal 6th-house chain, aggregated to a 0-100 score with bands LOW <25 / MODERATE <50 / ELEVATED <75 / HIGH ≥75. Flags: 6th CSL is Ketu or in Ketu's star (mystery illness — symptoms without findings), Rahu or in Rahu's star (wrong identification, drug reaction mimicking disease), CSL retrograde (diagnosis reverses on second opinion), Mercury afflicted (6/8/12 placement, node conjunction within 8°; its graded combustion is reported and adds no points, since a combust Mercury still signifies what it signifies in KP, F066), 6th cusp within 10 arc-min of a sub-lord boundary (CRITICAL ≤6' — reports the alternate sub lord and how the disease read would differ), Saturn in the CSL chain (delayed diagnosis), and the 10th CSL (the physician) signifying 6/8/12 at L1/L2 (change of doctor advised). Returns secondOpinionRecommended and physicianChangeIndicated. Supplementary lens, not medical advice or diagnosis.

Parameters

NameTypeRequiredDescription
birth_datetimestringYesBirth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitudenumberYesBirth location latitude. Range: -90 to 90.
longitudenumberYesBirth location longitude. Range: -180 to 180.
utc_offset_minutesnumberYesUTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsaenum: kp | kp_new | lahiri | raman | true_chitra | khullarNoAyanamsa 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_misdiagnosis_risk",
    "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.