Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Chart and reference

House strength index: the five-factor 0-100 score per house [Lumin index]

get_house_strength_index

A Lumin index, not KP and not a BPHS computation: a 0-100 score for each of the twelve houses, summed from five factors, 'occupants' (0-25: each occupant scored by dignity, combustion, motion and natural benefic class; an empty house 5), 'csl_strength' (0-30: the cuspal sub lord's dignity, combustion, motion and placement, and whether it also lords the cusp's sign), 'house_lord_placement' (0-20: the cusp sign's lord by the house it occupies), 'aspects' (0-15: from a neutral 7, each graha drishti offset falling within the orb of the Placidus cusp adds 5 for a benefic and takes 3 for any other planet, plus up to 2 for a close orb) and 'self_reference' (0-10: whether the CSL signifies its own house), graded VERY_STRONG (80+), STRONG (60+), MODERATE (40+), WEAK (20+), VERY_WEAK. Returns '{ chart_info, nodeDrishtiReading, house_strength: { scores: [{ house, total_score, factor_scores: { occupants, csl_strength, house_lord_placement, aspects, self_reference }, verdict, csl_planet, occupants, house_lord, house_lord_placed_in, stellium_detected, stellium_note, notes }], retrograde_reading: { applied, rule, retrograde_planets, astronomical, differs }, summary: { strongest_houses, weakest_houses, average_score, stellium_houses } }, houseConvention }'. The aspects factor reads the degree-exact aspects under 'nodeDrishtiReading' (the node reading used, default the 7th only); 'houseConvention' names the Placidus houses it is scored on and every planet whose house differs under whole sign. The motion deductions read KP motion, the nodes never retrograde ('retrograde_reading', with the astronomical flag beside). The weights are the engine's own and carry no source label yet (F031, F036). Built from natural benefic and malefic class, dignity and combustion, which KP judges by none of: reference and cross-system comparison only, never an input to a KP verdict. For the BPHS ch. 27 figure use 'get_shadbala'; for the house index of three components use 'get_bhava_bala'. The same block 'get_aspects_and_strength' returns as 'house_strength'.

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.
node_drishti_readingunknownNoWhich stated reading gives Rahu and Ketu their aspects for the aspects factor (F175). Default `seventh` (derived). The others: `none` (modern), `fifth-seventh-ninth` (modern), `rahu-5-7-9-12` (later), `rahu-5-7-9-ketu-3-7-10` (the Ketu half unsourced). The same parameter get_aspects_and_strength takes.

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