Birthstar Vedic Astrology MCP

Compute a full Vedic natal chart and cache it, returning a short handle. Call this FIRST. It returns a `chart_id` plus a small summary. Pass that chart_id to the other tools (get_grahas, get_houses, get_current_dasha, get_panchanga, get_yogas) to read specific parts of the chart without recomputing it. Args: dob: Date of birth, YYYY-MM-DD (proleptic Gregorian). tob: Time of birth, HH:MM or HH:MM:SS, 24-hour, local to `tz`. tz: IANA timezone name (e.g. "Asia/Kolkata") or fixed offset "+05:30". lat: Latitude in decimal degrees, North positive. lon: Longitude in decimal degrees, East positive. ayanamsha: Sidereal zero-point — lahiri, raman, kp, true_chitra, yukteshwar, or fagan_bradley. house_system: wh

Get planetary positions for a cached chart. Args: chart_id: Handle returned by create_chart. planets: Optional list of names to fetch (e.g. ["Moon", "Saturn"]). Defaults to the 9 classical grahas. Also accepts the outer bodies Uranus, Neptune, Pluto, Ceres, Pallas, Juno, Vesta, Chiron. detail: "basic" (default) or "full". Full adds the KP sub-lord and sub-sub-lord, navamsa sign, compound friendships, avasthas, gandanta/pushkara flags, natural karaka and daily motion. Per planet: sign, degrees, nakshatra + pada + lord, house (whole-sign), retrograde flag, and dignity state (exalted/debilitated/own/friend/etc).

Get the 12 houses (bhavas) for a cached chart. Args: chart_id: Handle returned by create_chart. method: "whole_sign" (default) — sign, lord, lord placement, karaka, occupants. "bhava_chalit" — Sripati/Porphyry cusps with degree spans, which can place a planet in a different house than whole-sign does. "kp_cusps" — Placidus cusps with sub-lords. Always includes an `analysis` block: each planet's functional nature for this ascendant (benefic/malefic/mixed by the houses it rules), plus the Baadhaka and Maraka houses and lords.

Get the currently-running dasha periods for a cached chart. Returns the active lord at every nested level (Maha -> Antar -> Pratyantar -> Sukshma -> Prana) for each dasha system the engine computed, with the ISO start/end dates of each period. NOTE: "current" is evaluated against the transit date baked into the chart when it was computed, not against today's date at call time.

Walk the dasha tree — list periods at any level, past or future. Use this for "when does my next antardasha start", "what runs after this mahadasha", "when was I in Jupiter". get_current_dasha only tells you what is running now; this gives you the whole sequence. Args: chart_id: Handle returned by create_chart. system: vimshottari (default), yogini, ashtottari, or chara_jaimini. within: Drill down by naming the enclosing lords, outermost first. None (default) lists the mahadashas. ["Sun"] lists the antardashas inside the Sun mahadasha. ["Sun", "Mercury"] lists the pratyantardashas inside that antardasha. Chara Jaimini is keyed by rashi name rather than graha. Each period carries lord, ISO start/e

Get the turning points between two dates — dasha changes and slow-planet ingresses. This is the two-clocks view: the dasha sequence counted from birth (which theme is switched on) against gochara, the real sky on that date (the trigger). Use it for "what happens in the next five years", "when does this period change", "when does Saturn cross my Moon". get_dasha_periods answers when one clock changes; this answers when both point at the same thing. Every date is exact, bisected against the ephemeris to the day — not a sampled approximation. Args: chart_id: Handle returned by create_chart. The birth data is reused; the range below is independent of the chart's transit_date. start_date: YYYY-MM-DD, inclusive. end_date: YYY

Get the chart angles, special lagnas, Arudha padas and Bhrigu Bindu. Beyond the ascendant: MC/IC/Descendant/Vertex, the time-based special lagnas (Bhava/Hora/Ghati/Sree/Indu), the Jaimini Arudha padas (AL, A2-A12, Upapada) and Bhrigu Bindu. Special lagnas whose rate is school-divergent are reported under `not_computed` with a reason rather than guessed.

Get the birth panchanga (the five limbs of the Vedic calendar). Returns tithi (lunar day + paksha), vara (weekday), nakshatra, yoga, and karana at the moment of birth, plus the lunar month and season.

Get the yogas (classical planetary combinations) present in a chart. Only yogas whose rule actually tested true are listed, each with the rule that matched. An empty list is a real result — it means none of the implemented yogas are present in this chart, not that the check was skipped.

Get one divisional chart (varga) from a cached chart. Args: chart_id: Handle returned by create_chart. varga: Which divisional chart, e.g. "D9" (navamsa), "D10" (dashamsa), "D11", "D60". See describe_chart -> varga_coverage for the full list of what this engine computes and what it deliberately does not. Returns the varga ascendant and each planet's sign in that chart. Where a varga's counting scheme diverges between schools, the scheme actually used is reported in `method` — do not assume it matches your tradition.

Get Vimsopaka bala — each planet's dignity-weighted strength across the 16 vargas. Use this to answer "which planets are strong across the divisional charts?" A planet in its own or exalted sign in all sixteen scores the full 20. Returns the score, the ceiling actually applicable, and an interpretive band. The score is the classical quantity; the band labels are a convention laid over it and are tagged as such.

Get Shadbala, Bhava Bala and Ishta/Kashta phala — how strong each planet and house is. Call this for "which planet is strongest", "is Saturn strong enough", or "which houses are weak". Shadbala is the six-fold Parasari strength; a planet meets expectation when `ratio` >= 1. Read `ratio` (>= 1 means the planet clears its own bar) and `rank_by_ratio` when saying a planet is strong or weak; the summary's `meets_requirement` lists every planet that qualifies. Each planet has its own `required_rupa`, so plain `rank` (absolute `total_rupa`) frequently disagrees: a planet can clear its own bar and still rank low overall. Use `strongest_by_ratio` / `weakest_by_ratio` for interpretation; the bare `strongest` / `weakest` keys are absolute-rupa based and kept