Muhurta
asterwise_get_muhurta
Searches a date span for top-scoring muhurta windows for a named activity using Panchanga, Choghadiya, and classical siddhi flags at a location.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
location | object | yes | For tools that need location but not birth time. Fields: date, lat, lon*, timezone, response_format |
activity | string | yes | |
from_date | string | yes | |
to_date | string | yes |
What it covers
Evaluates marriage, travel, griha_pravesh, business, education, medical, and vehicle_purchase (exact spellings upstream). Returns scored windows with tithi, nakshatra-related yoga name (Panchanga yoga, not natal yogas), vara, choghadiya metadata, boolean guards (rahu kaal, abhijit, amrita/sarvartha siddhi), and textual reasons. Unsupported activity strings are rejected upstream. It does not return a full month calendar (asterwise_get_panchanga_calendar) or only Choghadiya rows (asterwise_get_choghadiya).
Workflow
BEFORE: None — this tool is standalone.
AFTER: asterwise_get_panchanga — drill into Panchanga limbs for a chosen winning date.
Input
activity must be one of the supported English slugs above — not validated locally; bad values become MCP INTERNAL_ERROR. from_date/to_date ordering and span rules are enforced upstream. Location coordinates reuse LocationInput validation for lat/lon/date pattern.
Output contract
data.event_type (string)
data.from_date (string)
data.to_date (string)
data.timezone (string)
data.ayanamsa (string)
data.total_windows_evaluated (int)
data.top_windows[] — each:
date (string — YYYY-MM-DD)
start (string — HH:MM local)
end (string — HH:MM local)
score (int — 0–100)
choghadiya (string)
choghadiya_type (string)
yoga (string — Panchanga yoga name)
vara (string)
vara_number (int — 1–7)
tithi (string)
tithi_number (int — 1–30)
is_rahu_kaal (bool)
is_abhijit (bool)
is_amrita_siddhi (bool)
is_sarvartha_siddhi (bool)
reason (string)
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):
— Invalid LocationInput date/lat/lon → MCP INVALID_PARAMS
INVALID_PARAMS (upstream):
— None — bad activity, range, or ordering surfaces as MCP INTERNAL_ERROR at the tool layer.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— Panchanga yoga names here are not asterwise_get_yogas natal yogas.
Do not confuse with
asterwise_get_choghadiya — enumerates all Choghadiya for one day without activity scoring across a span.
asterwise_get_panchanga — single-day limb detail, not ranked muhurta search.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.