Advanced techniques
Vimsopaka Bala, 20-Fold Strength [Vedic Parashari]
get_vimsopaka_bala
[Vedic Parashari adjunct] 20-fold strength of each planet across all sixteen Shodasavarga vargas, weights summing to exactly 20 (D1 3.5, D9 3, D60 4, the rest tapering to 0.5). Each varga is graded on the classical varga-viswa ladder, own 20 / friend 15 / neutral 10 / enemy 7, which is a FRIENDSHIP ladder with no exaltation or debilitation rung. Grading uses the naisargika maitri alone where the classical method uses the compound panchadha, so the great-friend (18) and great-enemy (5) rungs are unreachable; the response states this in friendship and methodNote. Per-planet total 0-20 with band (EXCELLENT 17+, VERY_GOOD 14-17, GOOD 11-14, AVERAGE 8-11, POOR <8; the bands are a Lumin convention named in 'scoreProvenance', the total is the classical quantity), plus the grade each varga landed on. Two vargas are disputed in construction: D-60 is graded by the own-sign count and D-10 by even-from-9th ('vargaReadings'), and each planet's 'readingVariants' gives its total under every other reading, one varga swapped at a time, never averaged. 'weightedTotal' is the Shodasavarga; 'schemeTotals' gives each planet's total under all four schemes of BPHS 7.17-25, defined in 'schemes' with their classes: Shadvarga (6, 2, 4, 5, 2, 1), Saptavarga TWICE because which varga takes which of its values is disputed (the translators' tables, which every program uses, against BPHS 27.4's own order, which every textual check supports), Dasavarga (Rasi 3, Shashtiamsa 5, eight others 1.5, San 7.20), Shodasavarga. Each scheme sums to 20; schemes are different methods, never averaged. Rahu and Ketu are carried unranked. **'planets' and 'nodes' are paged together**: page N carries the Nth page of each, never cut inside a row; 'schemes', 'scoreProvenance', 'vargaReadings', 'methodNote' and 'summary' repeat on every page. The planetary 'report card'.
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. |
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_vimsopaka_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.