Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Bhava bala index, a Lumin 0-100 house strength index [Lumin extension]

get_bhava_bala_index

[Lumin extension] NOT the BPHS Bhava bala and not comparable with a printed one (F047): Lumin's own index per Placidus house, three 0-100 components averaged. Returns '{ houses: [{ house, lord, bhavadhipatiBala, drikBala, digBala, total, strengthBand: STRONG | MODERATE | WEAK, notes }], strongestHouse, weakestHouse, summary, method: 'lumin-strength-index', scoreProvenance, houseConvention }'. 'bhavadhipatiBala' is the cusp sign lord's score from 'get_shadbala_index' (itself an index, not virupas); 'drikBala' is an invented benefic/malefic count of aspects on the cusp; 'digBala' is a flat kendra bonus (100 for houses 1, 4, 7 and 10, 50 for the rest) and is NOT Bhava Digbala. Banded STRONG at 65 and MODERATE at 45, cuts with no source. 'scoreProvenance' names what is sourced (the three component names) and what is not. The house ORDER is the usable part. Say it is a Lumin index every time it is used. The classical virupas are 'get_classical_bhava_bala'. Gates no KP verdict. The same blocks 'get_bhava_bala' returns at its top level ('houses', 'strongestHouse', 'weakestHouse', 'summary', 'method', 'scoreProvenance', 'houseConvention').

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