Advanced techniques

Advanced Dasha Analysis

get_dasha_advanced

Advanced dasha analysis: stellium detection (mutual nakshatra network between MD/AD/PD lords), contradiction resolution (L1/L2 vs L3/L4 strength when lords conflict), Sookshma-Prana integration (hour-level timing using 4th and 5th dasha levels), and MD junction overlap windows (high-probability timing at mahadasha boundaries). **'sookshmaPrana.peakWindows' is paged**; 'stellium', 'contradiction', 'dashaOverlap' and 'summary' are small and repeat whole on every page, so read the verdicts from page 1 and page on only when you need more hour-level windows.

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	Event name for dasha analysis (default: Marriage). Ignored if house_group is provided.
house_group	array<house number (1-12)>	No	Override event lookup with explicit house numbers (1-12). When provided, event is ignored.
denial_group	array<house number (1-12)>	No	Houses that DENY the event (e.g., [1,5,9] deny marriage). Only used with house_group. If unsure, omit. The engine derives denial houses automatically from the event name.

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