Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Chart and reference

Aspects & Strength

get_aspects_and_strength

Planetary aspects + 5-factor house strength scores (0-100) + deep retrograde analysis. Returns '{ chart_info, aspects: { aspected_cusps: [{ house, aspecting_planet, aspect_type, orb, applying }], aspected_planets: [{ aspected_planet, aspecting_planet, aspect_type, orb, applying, mutual }], mutual_aspects, planet_aspect_summary }, house_strength: { scores: [{ house, total_score, factor_scores: { occupants, csl_strength, house_lord_placement, aspects, self_reference }, verdict }], summary }, retrograde_analysis: { retrograde_planets, station_planets, analyses }, houseConvention }'. 'aspect_type' is a graha drishti ordinal ('3rd', '4th', '5th', '7th', '8th', '9th', '10th', '12th'), never a Western aspect name. **Not KP.** The aspects are Parashari graha drishti (every planet the 7th; Mars 4/8, Jupiter 5/9, Saturn 3/10; Rahu and Ketu the 7th only by default, a derived reading), applied here as exact degrees with an orb against Placidus cusps rather than sign to sign (for the ch. 26 rule itself, sign to sign with the sputa virupas of each pair, use 'get_graha_drishti'), and 'houseConvention' names that convention and every planet whose house differs under whole sign. The strength score is built from natural benefic/malefic class, dignity and combustion, which KP judges by none of: it decides on the stellar signification chain and the cuspal sub lord. Reference and cross-system comparison only, never an input to a KP verdict. For full Shadbala (6-fold strength of planets) use 'get_shadbala'. For a Bhava bala index of houses (three components, a Lumin index and not the BPHS computation) use 'get_bhava_bala'. Whether the nodes cast graha drishti is stated five ways (F175): 'nodeDrishti' names the reading used and lists all five with their classes; pass 'node_drishti_reading' to recompute the node rows under another. Two of the three claims are also tools of their own, named in 'methodSeams': 'get_house_strength_index' (the 0-100 index, a Lumin index) and 'get_retrograde_verdicts' (the retrograde verdicts, Parashari). Call those when a reading needs one claim; this tool returns all three 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.
node_drishti_readingunknownNoWhich stated reading gives Rahu and Ketu their aspects (F175). Default `seventh` (the 'all planets' 7th applied to the nodes, derived). `none` (modern), `fifth-seventh-ninth` (modern), `rahu-5-7-9-12` (the Khemraj BPHS 51.26, later; Ketu not stated), `rahu-5-7-9-ketu-3-7-10` (the Ketu half unsourced). Changes the node rows, and through them the house index's aspects factor wherever a node's aspect falls within the cusp orb.

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