Dasha Transits
asterwise_get_dasha_transits
Combines active Vimshottari lords with transits on one date and returns scored correlations plus transit longitudes and houses from Moon and Lagna.
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 in YYYY-MM-DD format. |
target_time | string/null | no | HH:MM on target_date. Defaults to 12:00. |
target_timezone | string/null | no | IANA zone for target_date and target_time. Defaults to Asia/Kolkata. |
What it covers
Builds a snapshot for one date (today unless target_date is given): active Mahadasha, Antardasha, and Pratyantar; transiting planet positions; pairwise dasha–transit correlations with scores; and a filtered list of stronger correlations. Aspects are cast by the transiting planet (BPHS Ch.26). 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
target_date (string, optional — YYYY-MM-DD): date to analyse; defaults to today. target_time (string, optional — HH:MM, default 12:00) and target_timezone (IANA, optional — default Asia/Kolkata) set the instant on that date. All parameters are otherwise defined in the tool schema. 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.target_date (string — YYYY-MM-DD, the date analysed)
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 — conjunction | opposition | trine | square | special)
aspect_house (int — natal lord's sign counted from the transiting planet)
drishti (string or null — e.g. '3rd'; null for conjunction)
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):
— target_date not YYYY-MM-DD or target_time not HH:MM (schema pattern) → MCP INVALID_PARAMS
INVALID_PARAMS (upstream):
— Invalid target_date/target_time combination → upstream validation error, surfaces as MCP INTERNAL_ERROR.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— Without target_date the snapshot is for today; pass target_date for past or future days (e.g. tomorrow, a week view).
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.