Chart Strength
asterwise_get_chart_strength
Aggregates Shadbala, Bhavbala, Vimshopaka (with per-varga contributions), embedded sixteen vargas, Ashtakavarga, karaka maps, and graha yuddha pairs from BirthData.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
birth | object | yes | Birth data for a single person. Fields: date, time, lat, lon*, person_name, timezone, ayanamsa |
response_format | enum: markdown, json | no |
What it covers
Returns chart strength computations: six-planet Shadbala breakdowns with sthana/kala detail objects, twelve-house Bhavbala totals, Vimshopaka scores with threshold bands 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, vara, hora, ayana, total }
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, below 5 zero_capacity.
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.