Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Tajik Annual Dashas, Mudda and Patyayini [Tajik]

get_tajik_dashas

[Tajik] The two annual dashas of one year of life, on a tool of their own: the same block get_tajik_yogas returns as 'dashas' on its annual frame, byte for byte, so the two cannot disagree. **Mudda** is the Vimshottari compressed into a year (each planet's years times three, 360 days), opening on the lord given by (natal Moon nakshatra + completed years - 2) / 9 with the remainder counted from the Sun, which is the natal Moon's nakshatra progressed one a year (Adawal's and Narasimha Rao's worked examples; 'superseded' shows what the engine returned before 2026-09-28). The first period is a BALANCE from the natal Moon and the traversed part closes the year ('segment'). Three year lengths ship and none is preferred: 'periods' the stated 360 civil days, 'periodsScaledToYear' Adawal's proportional spread over the real interval between returns, 'periodsBySolarDegrees' a mudda day as the Sun's one degree (Narasimha Rao). 'annualMoonVariant' opens the year on the annual Moon's own nakshatra lord, a modern alternative. **Patyayini** is the one annual dasha native to Tajik: the year divided among the seven planets AND the lagna in ascending order of krishamsa (the longitude with the signs deleted), each period the year times its patyamsa over the highest krishamsa, nodes excluded; a longitude rule, not a strength rule. 'invariantHolds' reports the check the sources state. 'annual' names the year of life and the return instant ('returnInstant'). Mudda is a cross-check on the natal Vimshottari by its own doctrine, so read it with get_dasha_periods. Nothing is scored. Each dasha is also a tool of its own, named in 'methodSeams': 'get_mudda_dasha' and 'get_patyayini_dasha'. Call one when a reading needs one; this tool returns both.

Parameters

NameTypeRequiredDescription
birth_datetimestringYesBirth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitudenumberYesBirth location latitude. Range: -90 to 90.
longitudenumberYesBirth location longitude. Range: -180 to 180.
utc_offset_minutesnumberYesUTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsaenum: kp | kp_new | lahiri | raman | true_chitra | khullarNoAyanamsa system. Defaults to kp.
target_yearnumberNoThe year of life whose birthday falls in this calendar year (default: current year).

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