Advanced techniques
Mudda Dasha, the Tajik Annual Vimshottari (A46) [Tajik]
get_mudda_dasha
[Tajik] Mudda dasha for one year of life, on its own (CLASSICAL-SOURCES A46): the Vimshottari compressed into a year, each planet's Vimshottari years times three giving its days (360 in all), 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). Returns '{ frame: 'annual', annual: { targetYear, age, sunReturnDateUTC, returnInstant, chartLagnaSign }, mudda: { startingLord, startingLordDerivation, balance, startingLordUttaraKalamrita, uttaraKalamritaNote, annualMoonVariant, periods, periodsScaledToYear, periodsBySolarDegrees, superseded, residual, readWith, source, scalingSource }, methodNote }'; each period is '{ lord, days, startUTC, endUTC, segment, solarDegrees? }'. The first period is a BALANCE from the natal Moon and the traversed part closes the year ('segment': balance, whole, closing). 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); 'residual' says what the 360 leave open. 'annualMoonVariant' opens the year on the annual Moon's own nakshatra lord, a modern alternative. Mudda is a CROSS-CHECK by its own doctrine, read with the natal Vimshottari (get_dasha_periods), not a timing method alone. Nothing is scored. The same block 'get_tajik_dashas' returns as 'mudda' (and 'get_tajik_yogas' as 'dashas.mudda').
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. |
| target_year | number | No | The year of life whose birthday falls in this calendar year (default: current year). |
Example call
Send the request as a standard MCP tools/call:
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_mudda_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.