Core analysis

Pratyantardasha Periods

get_pratyantardasha_periods

Pratyantardasha (sub-sub-period, days) detail for ONE mahadasha, optionally narrowed to one antardasha within it. Returns that mahadasha's full nested tree: every antardasha with each of its pratyantardashas, with start and end dates. **This is the level KP timing actually resolves at.** The 3-lock rule requires the mahadasha, antardasha AND pratyantardasha lords to all signify the event's houses, so a timing verdict built on MD and AD alone is incomplete. 'get_dasha_periods' returns MD and AD for all 120 years; this returns the PD layer underneath one of them, because the whole PD tree for the full cycle does not fit a single response. Call it for the mahadasha your candidate window falls in, which 'get_smart_current_dasha' or 'find_event_timing_v2' will have named.

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.
mahadasha	planet name	Yes	Which mahadasha's pratyantardasha detail to return, by its lord, e.g. 'Rahu'.
antardasha	planet name	No	Optional: narrow to a single antardasha within that mahadasha, by its lord. Omit for every antardasha in the mahadasha.

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