Chart and reference

Annotated Dasha Timeline

get_annotated_dasha

Full Vimshottari timeline (mahadashas + antardashas) annotated with house significations and event-potential scoring for each period. Returns '{ moonNakshatra, mahadashas: [{ planet, startDate, endDate, signifiedHouses[], themes, isCurrent, eventPotential: [{ event, coverage, subLordGives }], subPeriods: [{ planet, startDate, endDate, signifiedHouses[], isCurrent, eventPotential }] }], queryDateUsed, pagination, pageNote }'. 'eventPotential' lists EVERY group the period lord reaches, with its 'coverage' (the percent of the group's houses the lord signifies), highest first, so a lord that reaches one house of a three house group is an entry at 33, not an omission; a group that is absent is one the lord signifies none of. 'isCurrent' is judged at 'query_date' (default: now), and 'queryDateUsed' says which instant that was and how it was read. **Paged by mahadasha**, each returned whole with its 9 antardashas, so one page is a complete life chapter rather than a partial one; 'queryDateUsed' rides on every page. Every period also names its lord's sub lord and the houses that sub lord signifies, and each 'eventPotential' entry says whether the sub lord reaches that group ('subLordGives'); name an 'event' and every period carries 'subLordJudgement' ('gives | negates | silent', Reader 3 canon p.151, Reader 6 canon p.294). The potentials themselves are this tool's own groups, not KP's. Use when: 'show me my full life timeline' / 'which dasha is best for X?'.

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.
event	event name	No	Optional. Judge every period lord's sub lord against this event's required and denial houses (`subLordJudgement` on each period).
query_date	string	No	The moment every period's `isCurrent` is judged at (default: now): which mahadasha and antardasha are running. 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_annotated_dasha",
    "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.