Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Core analysis

Vimshottari Dasha Periods

get_dasha_periods

Compute Vimshottari dasha, KP's 120-year planetary period system. Levels: mahadasha (main period, years), antardasha (sub-period, months), pratyantardasha (sub-sub-period, days). Returns '{ mahadashas: [{ planet, startDate, endDate, subPeriods }], currentDasha: { mahadasha, antardasha, pratyantardasha } }'. **Returns mahadasha and antardasha by default. The full pratyantardasha tree for all 120 years does not fit one response, so for PD detail call 'get_pratyantardasha_periods' for the mahadasha you care about — do NOT skip PD, KP's 3-lock rule needs MD, AD and PD to all signify.** Use when: you only need raw dasha periods. For event-relevance scoring, prefer 'get_smart_current_dasha' or 'get_event_dasha'.

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.
depthenum: mahadasha | antardasha | pratyantardashaNoHow deep to compute. Defaults to antardasha.

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_dasha_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.