Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Shadbala (6-Fold Planetary Strength)

get_shadbala

[Vedic Parashari adjunct] TWO quantities, both returned, and the response says which is which. 'classical' is the real BPHS ch. 27 computation in VIRUPAS (60 to a rupa): Sthana broken into Uccha, Saptavargaja across seven vargas, Ojha-Yugma, Kendra and Drekkana; Dig by the 27.7 cusp arc; Kala into Nathonnatha, Paksha, Tribhaga, the four Abda/Masa/Vara/Hora period lords and Ayana from declination, plus the 27.20 graha-yuddha correction; Chesta from the eight motion states; Naisargika; Drik over the sputa drishti scale. Then the six are summed and compared against this planet's own required pinda at 27.32-33, with the 27.34-36 component gates and Ishta and Kashta phala. 'componentProvenance' names the one component that is NOT the classical quantity (Chesta, because 27.24-25 needs a mean planet of classical Indian theory this engine does not compute) and 'variants' carries five editorial disputes as separate totals saying what each one MOVES. The top-level six 0-100 scores are the older Lumin index, kept because other tools read it; 'divergence' reports how far the two RANKINGS disagree, which on a 40-chart set is a lot (the same strongest planet on 30% of charts). Rahu and Ketu are carried unranked: BPHS computes strength for the seven only. Never compare an index number with a printed Shadbala; the virupas under 'classical' are the comparable figures.

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.

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