Skip to main content

Choghadiya

asterwise_get_choghadiya

Splits a solar day into sixteen Choghadiya segments from sunrise/sunset at a location and labels each slot's quality, ruler, and local clock bounds.

Parameters​

ParameterTypeRequiredDescription
locationobjectyesFor tools that need location but not birth time. Fields: date, lat, lon*, timezone, response_format

What it covers​

Computes eight day and eight night Choghadiya periods with type (auspicious, highly auspicious, inauspicious), ruling planet, suitability text, and is_current flags. Boundaries follow actual sunrise/sunset for the timezone, so DST is implicit. It does not rank multi-day windows for named activities (asterwise_get_muhurta) or return full Panchanga limbs (asterwise_get_panchanga).

Workflow​

BEFORE: None — this tool is standalone.
AFTER: asterwise_get_rahu_kaal — optional inauspicious band overlay for the same date.

Input​

LocationInput enforces YYYY-MM-DD date and lat/lon ranges locally. All parameters are defined in the tool schema.

Output contract​

data.date (string)
data.sunrise (string — HH:MM local)
data.sunset (string — HH:MM local)
data.day_choghadiya[] — eight objects:
period (int — 1–8)
name (string)
type (string — 'auspicious', 'highly auspicious', or 'inauspicious')
ruling_planet (string)
suitable_for (string)
start (string — HH:MM local)
end (string — HH:MM local)
is_current (bool)
data.night_choghadiya[] — eight objects with the same fields

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 date or coordinates → MCP INVALID_PARAMS

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:
— Slots track sunrise/sunset, not fixed civil slices.

Do not confuse with​

asterwise_get_hora — twenty-four planetary horas, not sixteen Choghadiya.
asterwise_get_muhurta — scored windows across a date range for named activities.

Connect​

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