Transits
asterwise_get_transits
Lists sign ingresses and retrograde/direct stations for all planets between two dates against the natal context and returns chronological astronomical events.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
birth | object | yes | Birth data for a single person. Fields: date, time, lat, lon*, person_name, timezone, ayanamsa |
from_date | string | yes | Start of the window to list ingress and station events, YYYY-MM-DD. |
to_date | string | yes | End of the window to list ingress and station events, YYYY-MM-DD. |
response_format | enum: markdown, json | no | Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload. |
What it covers
Aggregates ingress rows (with sankranti flag for Sun) and station rows with Julian day, local ISO timestamps, and ecliptic longitude. The upstream API enforces ordering and a 24-month window; violations are not pre-checked in this MCP layer. It does not return today's full Gochar row (asterwise_get_gochar) or dasha-transit scores (asterwise_get_dasha_transits).
Workflow
BEFORE: RECOMMENDED — asterwise_get_natal_chart — clarifies the natal reference for the same birth data.
AFTER: asterwise_get_gochar — optional current snapshot after scanning the range.
Input
from_date and to_date are strings in the format expected by the upstream API (typically YYYY-MM-DD). Range cap (24 months), date order, and validity are enforced upstream, not locally.
Output contract
data.ingresses[] — each:
planet (string)
from_sign (int — 0–11)
to_sign (int — 0–11)
jd (float)
date_iso (string — ISO datetime, local time)
is_sankranti (bool — true for Sun ingresses only)
retrograde_ingress (bool)
data.stations[] — each:
planet (string)
station_type (string — 'retrograde' or 'direct')
jd (float)
date_iso (string — ISO datetime)
longitude (float)
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 — range/order violations surface as MCP INTERNAL_ERROR at the tool layer.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— Exceeding the 24-month cap or bad date order fails upstream and is not turned into MCP INVALID_PARAMS here.
Do not confuse with
asterwise_get_gochar — single-day transit snapshot with houses from Moon/Lagna, not ingress/station lists.
asterwise_get_dasha_transits — dasha lord vs transit scoring for today only.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.