Transit and timing

Dasha Lord Transit Triggers

get_dasha_lord_transit_triggers

Rule 1 at one moment: for each running dasha lord (Mahadasha, Antardasha, Pratyantardasha at query_datetime, default now), whether a transiting planet falls within 1 degree of the natal position of that lord's sub lord. One row per lord and transiting planet. Reads no event. Returns '{ queryDatetime, dashaTriggers: [{ triggered, dasha_lord, dasha_lord_natal_sub_lord, natal_sub_lord_longitude, transit_planet, transit_longitude, angular_separation, orb_threshold }] }'. The same block 'get_transit_analysis' returns as 'dashaTriggers'.

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.
query_datetime	string	No	The transit moment, ISO 8601 (default: now). The running dasha lords (Mahadasha, Antardasha, Pratyantardasha) are read at this same moment, not at the time of the call. 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_dasha_lord_transit_triggers",
    "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.