Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Bhava Bala, Net House Strength [Vedic Parashari]

get_bhava_bala

[Vedic Parashari adjunct] TWO QUANTITIES, and which is which. 'classical' is BPHS 27.26-31 in virupas (Santhanam; ch. 29 in Sharma), per bhava on the Sripati bhava madhya (its own 'houseConvention' says so): bhavadhipati, the lord's classical Shadbala total; bhava drishti bala on the sputa scale, a quarter of each benefic aspect added and each malefic one subtracted, with the Jupiter/Mercury clause in THREE readings, each labelled: their full aspect on top of the quarter ('mercuryJupiterFullPlusQuarter', the literal line and Sripati, disputed), in place of it ('mercuryJupiterInFull', Raman, disputed), and every aspect a quarter ('quarterOnly', no source for Bhava bala, legacy); Bhava Dig bala by the verse's four sign lists (deduct the 7th from Gemini, Virgo, Libra, Aquarius, Sagittarius 0-15; the 4th from Aries, Taurus, Leo, Sagittarius 15-30, Capricorn 0-15; the lagna from Cancer and Scorpio; the 10th from Capricorn 15-30 and Pisces; fold past 180, divide by 3), with Raman's reading beside (Cancer watery, 10 virupas per bhava, modern); the 27.30-31 adjustments, +60 for Jupiter or Mercury occupying, -60 for Saturn, Mars or the Sun, and +15 for a sirshodaya sign by day, a prishtodaya sign by night and Pisces, the one ubhayodaya sign, in twilight, whose length no edition states for this rule, so it ships in two readings (BPHS 9.14, 3 ghatis on the dark side; 46.44-46, 5 ghatis either side). 'totals' gives each bhava's Bhava bala under each stated reading (six BPHS combinations and Raman's own method), each with its reading, rupas and weakest source class, and 'readings' their methodology. There is no single total and no ranking. 'sumOfComputedLegs' is the pre-dig-bala sum, kept. The top level is the older Lumin index, not the BPHS computation: Bhavadhipati (the lord's index score from get_shadbala) + Drik Bala (cusp aspects) + Dig Bala, each 0-100 and averaged, banded STRONG at 65. Its Dig Bala column is a flat kendra bonus and is NOT Bhava Digbala; that is named in scoreProvenance rather than hidden. The index returns per-house entries plus strongest and weakest house, and its house ORDER is the usable part. Each quantity is also a tool of its own, named in 'methodSeams': 'get_classical_bhava_bala' (the BPHS virupas, paged by bhava) and 'get_bhava_bala_index' (the Lumin index). This tool returns both in one call.

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