Advanced techniques
Panchavargeeya Bala, Tajik's Five-Fold Strength (A43) [Tajik]
get_panchavargeeya_bala
[Tajik] Panchavargeeya bala on its own (CLASSICAL-SOURCES A43, from the Hayanaratna in Gansten's critical edition): each of the seven planets scored out of 80 across five components, kshetra, uccha, hadda, drekkana and navamsa. Four score the planet's relation to the lord of a division it occupies on one ladder (own the full maximum, a friend half, an enemy a quarter); uccha is continuous, (distance from the debilitation point / 180) x 20. Returns '{ frame: 'natal' | 'annual', annual?: { targetYear, age, sunReturnDateUTC, chartLagnaSign }, panchavargeeya: [{ planet, components: [{ component, maximum, virupas, virupasNeutralAsFriend, computed, divisionLord, relation, stated, source }], total, totalNeutralAsFriend, classified, classifiedNeutralAsFriend, band, bandNeutralAsFriend, ramanBand, neutralRungChangesBand, neutralRungAffects, statedTotal, notComputed, variants }], navamsaSignIndex, gaps, methodNote, pagination, pageNote }'. 'classified' is the total over four, the 0 to 20 scale the bands are defined on: Nirbali below 5, Madhya Bali 5 to 10, Poorna Bali 10 to 15, Parakrami above 15. **THE NEUTRAL RUNG IS STATED IN NO COMPONENT**, so both ends ship on every planet ('total' and 'totalNeutralAsFriend', 'band' and 'bandNeutralAsFriend'); the uccha reference point and the friendship scheme are named in 'variants'. 'gaps' lists what both Tajik strength systems leave open, each line prefixed with its system. It is A45's tie-break input but NOT the year lord: the aspect gate decides first (get_varshesha). Pass 'target_year' for that year's solar-return chart, or omit it for the natal chart. Nothing is ranked. **'panchavargeeya' is paged by planet.** The same block 'get_tajik_yogas' returns as 'bala.panchavargeeya'.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| birth_datetime | string | Yes | Birth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00"). |
| latitude | number | Yes | Birth location latitude. Range: -90 to 90. |
| longitude | number | Yes | Birth location longitude. Range: -180 to 180. |
| utc_offset_minutes | number | Yes | UTC offset in minutes (e.g., 330 for IST, -300 for EST). |
| ayanamsa | enum: kp | kp_new | lahiri | raman | true_chitra | khullar | No | Ayanamsa system. Defaults to kp. |
| target_year | number | No | Score the planets on that year's solar-return (annual) chart, Tajik's native frame. Omit for the natal chart. |
Example call
Send the request as a standard MCP tools/call:
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_panchavargeeya_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.