Chart and reference

Current Dasha Analysis

get_smart_current_dasha

Current running dasha (mahadasha + antardasha + pratyantardasha) annotated with house significations, themes, and percentage-scored event activations. Smarter than raw 'get_dasha_periods', converts MD/AD/PD lords into 'Marriage 100% active, Career 67% active, Travel 33% active' rankings. Returns '{ currentDasha: { md, ad, pd }, activatedHouses[], activeEvents: [{ event, activationPct }], themes[], rulingPlanetSync }'. Each running lord also carries its sub lord's signified houses and each activation group says whether each lord's SUB LORD reaches it ('subLords', 'gives' or 'silent'): KP judges a period lord by its sub lord (Reader 3 canon p.151, Reader 6 canon p.294), and the percentages beside it are this tool's own and unsourced. Name an 'event' for the full sub-lord judgement ('subLordJudgement', 'gives | negates | silent' against the event's required and denial houses). Use when: 'what period am I in?' / 'what's happening in my life now?'.

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 each running period lord's sub lord against this event's required and denial houses (`subLordJudgement`). Omitted: every level still reports its sub lord's houses.
query_date	string	No	The moment the running mahadasha, antardasha and pratyantardasha are read for, and `remainingDays` counts from (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_smart_current_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.