Gochar

asterwise_get_gochar

Computes Gochar against the natal Moon and Lagna and returns per-planet transit longitudes, houses, AVK scores, vedha flags, and a roll-up summary.

Parameters

Parameter	Type	Required	Description
birth	object	yes	Birth data for tools that need the exact birth time (no sunrise fallback). Required fields: date, time, lat, lon. Optional fields: 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.
target_date	string/null	no	Date to compute transits for, YYYY-MM-DD (at 12:00 India time). Defaults to today in India (Asia/Kolkata).

What it covers

Produces a transit snapshot: natal Moon and ascendant signs, nine graha transit rows with nakshatra/pada, houses from Moon and Lagna, favourability flags, optional Ashtakavarga bindu (null for Rahu/Ketu), vedha state (Vedha follows Phaladeepika Adhyaya 26: no vedha between the Sun and Saturn, nor between the Moon and Mercury; Rahu and Ketu neither cast nor receive vedha), a final quality verdict with matching interpretation and themes (the house-only reading kept in house_rule_* fields), plus summary counts and sade sati / chandra ashtama flags. It does not list ingress events over a range (asterwise_get_transits), correlate with Vimshottari (asterwise_get_dasha_transits), or return Panchanga elements.

Workflow

BEFORE: RECOMMENDED — asterwise_get_natal_chart — anchors what "natal" means for the same birth record.
AFTER: asterwise_get_dasha_transits — adds dasha-lord correlation for today.

Input

target_date (string, optional — YYYY-MM-DD): date to compute transits for; defaults to today if omitted. BirthData follows the global contract. Birth time is required: this tool has no sunrise fallback. If the user doesn't know it, say so rather than guessing; never pass time='00:00' for unknown.

Output contract

data.natal:
moon_sign (string)
moon_sign_index (int)
ascendant_sign (string)
ascendant_sign_index (int)
data.target_date (string — YYYY-MM-DD, today)
data.transits[] — nine objects (Sun through Ketu):
planet (string)
transit_sign (string)
transit_sign_index (int)
transit_degree (float)
is_retrograde (bool)
nakshatra (string)
nakshatra_pada (int)
house_from_moon (int — 1–12)
house_from_lagna (int — 1–12)
is_favorable_from_moon (bool)
is_favorable_from_lagna (bool)
vedha_active (bool)
vedha_blocking_planet (string or null)
ashtakavarga_score (int or null — raw Bhinna Ashtakavarga bindus 0–8 for the transit sign; 5+ forces favourable, ≤3 unfavourable; null for Rahu and Ketu)
ashtakavarga_score_reduced (int or null — Trikona-reduced value, reference only)
bindu_override (bool — true when the bindus (5+ / 3 or fewer) decided favourability instead of the house)
favorable_reason (string — which rule decided is_favorable_from_moon, in words)
quality (string — final verdict 'favorable' or 'unfavorable'; always matches is_favorable_from_moon, bindu override included)
interpretation (string — agrees with quality: the classical house text, or favorable_reason when the bindus reverse the house rule)
themes[] (string array — house themes; empty when the bindus reverse the house rule)
house_rule_quality (string — the house from the Moon alone, before the bindu override)
house_rule_interpretation (string — classical text for the house alone)
house_rule_themes[] (string array — themes for the house alone)
data.summary:
favorable_count (int)
unfavorable_count (int)
vedha_blocked_count (int)
overall_score (int)
sade_sati_active (bool)
sade_sati_phase (string or null)
sade_sati_interpretation (object or null — populated when sade_sati_active is true; contains phase-specific prose for rising, peak, or setting phase of Sade Sati)
chandra_ashtama_active (bool)

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

Errors

INVALID_PARAMS (local — caught before upstream call):
— target_date must match YYYY-MM-DD when provided (Pydantic pattern on the tool schema) → MCP INVALID_PARAMS

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:
— ashtakavarga_score is null for Rahu and Ketu.

Do not confuse with

asterwise_get_transits — ingress and station tables for a chosen date window, not a single-day Gochar snapshot.
asterwise_get_dasha_transits — scores how transits meet active dasha lords, not the full nine-planet Gochar row set.

Connect

Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.