Chart Strength
asterwise_get_chart_strength
Aggregates the chart's strength measures from BirthData: Shadbala, Bhavbala and Vimshopaka (with per-varga contributions). Also returns the sixteen vargas, Ashtakavarga, karaka maps and graha yuddha pairs.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
birth | object | yes | Birth data for a single person. Required fields: date, lat, lon. Optional fields: time, person_name, timezone, ayanamsa. |
response_format | enum: markdown, json | no | Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload. |
What it covers
Returns chart strength computations: seven-planet (Sun–Saturn) Shadbala breakdowns with sthana/kala detail objects, twelve-house Bhavbala totals, Vimshopaka scores with threshold bands (BPHS scoring: own sign 20, otherwise 18/15/10/7/5 by relationship with the sign lord) and per-D1..D60 fractions, full divisional chart mirror of asterwise_get_divisional_chart, Ashtakavarga mirror of asterwise_get_ashtakavarga, karaka_to_planet / planet_to_karaka, and graha_yuddha.war_pairs. It does not label named yogas (asterwise_get_yogas) or doshas (asterwise_get_doshas).
Workflow
BEFORE: RECOMMENDED — asterwise_get_natal_chart — contextualises houses before reading bala tables.
AFTER: asterwise_get_yogas — optional configuration pass after strength review.
Input
BirthData only; no extra toggles.
Output contract
data.shadbala — keyed by Sun..Saturn (excludes Rahu/Ketu):
planet (string)
sthana_bala, dig_bala, dig_bala_virupas, dig_bala_rupas, kala_bala, cheshta_bala, naisargika_bala, drik_bala, yuddhabala_adjustment, total (float), ratio (float), required_minimum (float), is_purna_bala (bool)
sthana_bala_details — { uchcha, saptavargaja, ojhayugma, kendradi, drekkana, total }
kala_bala_details — { nathonnatha, paksha, tribhaga, abda, masa, vara, hora, ayana, total }. Sun and Moon cheshta_bala is 0: their BPHS Cheshta is counted in Kala Bala (Sun's ayana and Moon's paksha doubled, 0–120), as in B.V. Raman and JHora. ayana uses the kranti of the ecliptic longitude (0–60). Paksha uses the chart's natures: a waning Moon is malefic (strongest near Amavasya) and Mercury follows his companions, as in JHora.
data.bhavbala — keys '1'..'12':
bhavadhipati_bala, bhava_dig_bala, bhava_drik_bala, total (float)
data.vimshopaka_bala — keyed by planet including Rahu/Ketu:
vimshopaka_score (float, max 20)
threshold (string — 'zero_capacity', 'moderate', 'good', or 'extremely_auspicious')
per_varga — keyed by D1..D60: { contribution (float), fraction (float) }
data.divisional_charts — same nested schema as asterwise_get_divisional_chart
data.ashtakavarga — same schema as asterwise_get_ashtakavarga
data.karakas — { karaka_to_planet{}, planet_to_karaka{} }
data.graha_yuddha — { war_pairs[] }
Threshold guide: 15+ extremely_auspicious, 10–15 good, 5–10 moderate (BPHS minimum is 5.0, so zero_capacity — below 5 — is kept for compatibility but never occurs).
Response format
response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode.
Compute class
MEDIUM_COMPUTE (~800ms)
Errors
INVALID_PARAMS (local — caught before upstream call):
None — BirthData only; Pydantic handles field bounds.
INVALID_PARAMS (upstream):
— None — upstream rejection surfaces as MCP INTERNAL_ERROR at the tool layer.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— Large payload due to embedded vargas and Ashtakavarga duplicates.
Do not confuse with
asterwise_get_yogas — boolean yoga catalogue, not numeric bala.
asterwise_get_ashtakavarga — standalone AVK when strength bundle is not needed.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.