Advanced techniques

K.N. Rao Triple-Dasha Consensus Workflow

run_triple_dasha_consensus

Cross-validates event timing across THREE independent dasha systems: Vimshottari (event-filtered) + Yogini (36-yr) + Jaimini Chara (sign-based). Finds calendar windows where multiple systems independently flag the same time range. Returns '{ vimshottariWindows[], yoginiCurrent, charaCurrent, convergenceWindows: [{ startDate, endDate, systemsAgreeing: 1|2|3 }], convergenceLevel: STRONG|PARTIAL|WEAK|DIVERGENT }'. Pattern B. Per K.N. Rao 'Finer Techniques of Astrological Predictions'.

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	string	No	Event to time (e.g. 'Marriage'). Default: Marriage.
query_date	string	No	ISO date (default: now).
top_windows	number	No	Top N Vimshottari windows to check (default: 5).

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": "run_triple_dasha_consensus",
    "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.