Advanced techniques

Conditional Nakshatra Dashas (BPHS ch. 46): which of the nine applies, and its timeline

get_conditional_dashas

Parashari, not KP. Brihat Parashara Hora Shastra ch. 46 names nine nakshatra dashas beside Vimshottari and says they are 'followed in special cases' (vv. 2-5): Ashtottari, Shodashottari, Dwadashottari, Panchottari, Shatabdika, Chaturashiti-sama, Dwisaptati-sama, Shashtihayani, Shat-trimshat-sama, and gives Yogini (vv. 195-199) with no case. This tool evaluates every one of the text's conditions on the chart (vv. 17-43: Rahu's place from the lagna lord, day or night birth with the paksha, the lagna's hora, the navamsa and dwadasamsa lagna, vargottama, the 10th lord in the 10th, the lagna lord in the 7th or the 7th lord in the lagna per the Sanskrit of v. 38, with Santhanam's English reading reported as a labelled mistranslation variant in 'variantReadings', the Sun in the lagna) and returns 'applicability' for all nine with the verse and the reason, 'applicable' naming those that hold, and a full timeline for each applicable system: starting lord with the counting shown, the balance at birth (v. 16, or vv. 21-22 for Ashtottari), and periods to 120 years. Pass 'system' to get one system's timeline whether or not its condition holds. Shodashottari's two readings are reported separately. Where the text's table gives a nakshatra no lord (Shashtihayani omits Chitra) the timeline says so rather than guessing. Houses are whole-sign, as the text defines them. No effect is emitted. Edition stated (Santhanam 1984; Sharma numbers this ch. 48).

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.
system	enum: ashtottari \| shodashottari \| dwadashottari \| panchottari \| …	No	One system to compute regardless of its condition. Omit to get the timelines of every system whose condition holds.
query_date	string	No	ISO date to mark the current period (default: now). Send a zone (Z, or +hh:mm as in 2026-10-20T10:30:00+05:30). A value without a zone is read as UTC, never as local time, and a date alone is midnight UTC. This is a different moment from judgement_datetime, which is a local wall clock sent with its own offset.

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