Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Sudarshana dasha (BPHS ch. 74 vv. 21-26): the year and month bhava for a date

get_sudarshana_dasha

Parashari, not KP. The Sudarshana dasha of Brihat Parashara Hora Shastra ch. 74 vv. 21-26 (Santhanam; ch. 76 in Sharma), on its own: each whole-sign bhava from the lagna rules one year in turn from birth, the 1st first, twelve years repeating, and within each year a bhava rules each month. For 'at' (defaulting to now) returns 'dasha' (the year-lagna bhava, the month bhava, the age, and the vv. 24-26 assessment lists read with the year-lagna as the 1st: benefics in kendras, trikonas and the 8th, bhavas held by the nodes alone, benefics in the 6th or 12th, malefics in the 3rd, 6th and 11th), the year-lagna's and month's sign and lord, 'currentRound.years' (the twelve years of the current round with dates) and 'monthsOfYear' (the twelve months of the current year with dates, the first being the year's own bhava: v. 23, 'the antardashas beginning from that', decided by the worked examples of Sharma, the Sudha commentary and P.V.R. Narasimha Rao 2001). The count from the 1st bhava every year, which this tool gave until 2026-09-28, rides beside as 'monthCountFromFirst' and 'monthsOfYearCountFromFirst', labelled unsourced (F176). The 'dasha' block is identical to get_sudarshana_chakra's, computed by the same function; read get_sudarshana_chakra for the three-ring judgement of the bhavas themselves. THE GATE TRAVELS WITH IT: vv. 19-20 say the chakra is used only when the Sun, the Moon and the lagna are in three different signs, and 'applicable' with its reason is returned. 'conventions' states what the verses do not fix: a year is 365.25 days from the birth instant and a month a twelfth of it, the engine's own convention (the commentaries reckon a solar return with solar-ingress months, which is not computed), and the month rule with its sources. Edition stated. No score. Gates no KP verdict.

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.
atunknownNoISO 8601 date-time for which to read the Sudarshana dasha (vv. 21-26). Defaults to now.

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_sudarshana_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.