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 a single person. Fields: date, time, lat, lon*, person_name, timezone, ayanamsa
response_format	enum: markdown, json	no
target_date	string/null	no

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, interpretation strings, themes, and quality labels, 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 (time='00:00' accepted without unknown-time detection).

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)
bindu_override (bool)
vedha_active (bool)
vedha_blocking_planet (string or null)
ashtakavarga_score (int or null — null for Rahu and Ketu)
interpretation (string)
themes[] (string array)
quality (string — 'favorable' or 'unfavorable')
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.