Rahu Kaal
asterwise_get_rahu_kaal
Computes Rahu Kaal, Gulika Kaal, and Yamaganda Kaal intervals from diurnal length at a location and marks whether Rahu Kaal is active now in local time.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
location | object | yes | For tools that need location but not birth time. Required fields: date, lat, lon. Optional fields: timezone, response_format. |
What it covers
Returns sunrise/sunset anchors plus three inauspicious bands with start, end, duration_minutes (~93 for Rahu Kaal), and is_active on Rahu Kaal. Polar day or night (no sunrise or sunset) is not an error: data.status is no_sunrise, data.status_detail says why, and the time fields are left out. It does not return Panchanga tithi/nakshatra (asterwise_get_panchanga) or scored muhurta search (asterwise_get_muhurta).
Workflow
BEFORE: None — this tool is standalone.
AFTER: asterwise_get_choghadiya — broader auspicious/inauspicious grid for the day.
Input
LocationInput validates date pattern and coordinates locally.
Output contract
data.date (string)
data.sunrise (string — HH:MM local), sunrise_at / sunrise_utc (ISO 8601 with date; the same for sunset and every start/end below as start_at / start_utc)
data.status (ok | no_sunrise — polar day or night: no time fields, not an error)
data.status_detail (string — present when status is no_sunrise: polar day or night, the date and the latitude)
data.sunset (string — HH:MM local)
data.rahu_kaal:
start (string — HH:MM local)
end (string — HH:MM local)
duration_minutes (int — typically 93)
is_active (bool)
data.gulika_kaal — same shape as data.rahu_kaal
data.yamaganda_kaal — same shape as data.rahu_kaal
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
FAST_LOOKUP
Errors
INVALID_PARAMS (local — caught before upstream call):
— Invalid LocationInput fields → MCP INVALID_PARAMS
INVALID_PARAMS (upstream):
— None for polar dates: they answer with status no_sunrise, not an error.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— Polar day or night returns status no_sunrise with status_detail naming polar day or night, the date and the latitude; the sunrise, sunset and kaal fields are left out.
Do not confuse with
asterwise_get_choghadiya — full day/night slot tables, not only the three kaal bands.
asterwise_get_panchanga — Panchanga limbs, not kaal timers.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.