Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Rasi Dashas (BPHS ch. 46 vv. 158-190): Chara, Sthira, Yogardha, Kendradi, Karaka, Manduka, Shula, Trikona, Drig, Lagnadi

get_rasi_dashas

Parashari, not KP. The ten sign-based dashas Brihat Parashara Hora Shastra gives in ch. 46, each period carrying its verses: Chara in the text's own reading (direction from the 9th house's pada, v. 167; years counted from a rasi to its lord, onwards from a vishama-pada rasi and in reverse from a sama-pada one, the dual-lorded rasis to the stronger lord by the vv. 158-166 ladder, +1 or -1 for an exalted or debilitated planet in the counted-to rasi); Sthira from the Brahma graha's rasi at 7, 8, 9 years by class (vv. 168-173, the Brahma graha's candidates and refusals listed); Yogardha as the mean of the two (v. 174); Kendradi, kendras then panaparas then apoklimas by strength from the stronger of lagna and 7th (vv. 175-177, the lagna-kendradi form some call Narayana); Karaka from the Atmakaraka in karaka order (v. 178); Manduka by jumps of three (vv. 179-180); Shula from the stronger of 2nd and 8th (vv. 181-182); Trikona from the strongest trine (vv. 183-184); Drig by the 9th, 10th and 11th and the rasis they aspect (vv. 185-187); Lagnadi from the lagna advanced by the Moon's nakshatra fraction, with the one balance at birth the text states (vv. 188-190). Every system carries 'assumptions' naming what the text leaves open (Drig and Lagnadi state no year rule, Karaka's count is read inclusive, Manduka's wording does not fit a twelve-rasi jump). Returns the Brahma graha and the BPHS Chara years for all twelve rasis as shared inputs. get_chara_dasha carries the Jaimini Sutras reading and reports this one beside it; neither is picked. Whole-sign houses. No effect is emitted. Edition stated (Santhanam 1984; Sharma numbers this ch. 48).

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.
systemenum: chara | sthira | yogardha | kendradi | …NoOne system. Omit for all ten.
query_datestringNoISO date to mark the current period (default: 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_rasi_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.