Dasha Transits

asterwise_get_dasha_transits

Combines active Vimshottari lords with today's transits and returns scored correlations plus transit longitudes and houses from Moon and Lagna.

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

Builds a snapshot for the current calendar day (no date parameter): active Mahadasha, Antardasha, and Pratyantar; transiting planet positions; pairwise dasha–transit correlations with scores; and a filtered list of stronger correlations. It does not return full Dasha trees (use asterwise_get_dasha), ingress calendars (asterwise_get_transits), or standalone Gochar without Dasha context (asterwise_get_gochar).

Workflow

BEFORE: RECOMMENDED — asterwise_get_natal_chart — same birth data should be understood before interpreting houses and lords.
AFTER: asterwise_get_gochar — optional broader transit snapshot without dasha scoring.

Input

No date field — "today" is fixed by the API. All parameters are otherwise defined in the tool schema. BirthData follows the global contract (unknown birth time: time='00:00' accepted without detection).

Output contract

data.target_date (string — YYYY-MM-DD, today)
data.active_dasha:
start_date (string)
end_date (string)
maha — { planet (string), start_date (string), end_date (string) }
antar — { planet (string), start_date (string), end_date (string) }
pratyantar — { planet (string), start_date (string), end_date (string) }
data.transit_positions{} — keyed by planet name:
rashi_index (int)
rashi (string)
is_retrograde (bool)
house_from_moon (int)
house_from_lagna (int)
data.correlations[] — each object:
dasha_level (string)
dasha_lord (string)
transit_planet (string)
aspect_type (string)
score (int — 1=mild, 2=moderate, 3=high)
natal_rashi (string)
transit_rashi (string)
is_retrograde (bool)
significance (string)
data.periods_of_significance[] — same shape as correlations[] filtered to score ≥ 2

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):
None — all validation is upstream.

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:
— Target date is always "today"; past/future analysis is not supported by this tool.

Do not confuse with

asterwise_get_gochar — full nine-planet Gochar with AVK and vedha fields, without dasha–transit correlation scores.
asterwise_get_transits — ingress and station lists over a chosen range, not today's dasha snapshot.
asterwise_get_dasha — full Vimshottari tree without transit overlay.

Connect

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