Asterwise

Festival Calendar

asterwise_get_festival_calendar

Read-onlyIdempotent

Computes all major Hindu festival dates for a given year and location. Returns 20 pan-Hindu festivals including solar sankrantis (Makar Sankranti, Vaisakhi) and tithi-based festivals (Diwali, Holi, Dussehra, Janmashtami, Ganesh Chaturthi, Ram Navami, and 12 others).

WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_panchanga — drill into full Panchanga detail for any specific festival date.

INPUT CONTRACT: year: integer 1900-2100. Either location (city name) OR latitude + longitude + timezone must be provided.

DO NOT CONFUSE WITH: asterwise_get_panchanga_calendar — full Panchanga for every day of a month; not festival-specific. asterwise_get_muhurta — finds auspicious windows for activities; not a festival calendar.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-festival-calendar/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes	Four-digit calendar year, e.g. 2026.
`latitude`	No	Latitude in decimal degrees, north positive (e.g. 13.08).
`location`	No	Place name, e.g. 'Chennai, India'. Alternative to giving latitude, longitude and timezone.
`timezone`	No	IANA time zone name, e.g. 'Asia/Kolkata'.
`longitude`	No	Longitude in decimal degrees, east positive (e.g. 80.27).
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

changedInput schema / properties / year / description

Previous value: -"Four-digit calendar year, e.g. 2026. Defaults to the current year when omitted."New value: +"Four-digit calendar year, e.g. 2026."

Changed6 schema fields changedSep 5, 2026

addedInput schema / properties / latitude / description

Added value: +"Latitude in decimal degrees, north positive (e.g. 13.08)."

addedInput schema / properties / location / description

Added value: +"Place name, e.g. 'Chennai, India'. Alternative to giving latitude, longitude and timezone."

addedInput schema / properties / longitude / description

Added value: +"Longitude in decimal degrees, east positive (e.g. 80.27)."

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

addedInput schema / properties / timezone / description

Added value: +"IANA time zone name, e.g. 'Asia/Kolkata'."

addedInput schema / properties / year / description

Added value: +"Four-digit calendar year, e.g. 2026. Defaults to the current year when omitted."

Changed2 schema fields changedSep 4, 2026
- addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```
- changedInput schema / required
```
Previous value: -[
-  "year",
-  "response_format"
-]New value: +[
+  "year"
+]
```
AddedMay 3, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false) are present and consistent with the description. The description adds extra context about output format options (markdown vs json) and references a full contract URL, going slightly beyond what the annotations alone convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear labeled sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH) and is appropriately concise. The only minor redundancy is the repeated mention of the 20 festival count, but this does not detract from clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich schema (6 params, 100% coverage, enum, output schema) and annotations, the description provides sufficient additional context including the full documentation URL, usage alternatives, and output format behavior. It is complete for an agent to correctly invoke and understand the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already has descriptions for all 6 parameters (year, latitude, location, timezone, longitude, response_format), making coverage 100%. The description reinforces the meaning of the location alternative and the response_format enum, adding value beyond the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Computes'), the resource (major Hindu festival dates), and the scope (for a given year and location). It explicitly lists example festivals (Makar Sankranti, Diwali, Holi, etc.) and names the sibling tools it should not be confused with, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly explains when to use this tool versus the alternatives: it directs users to asterwise_get_panchanga for full Panchanga detail on a specific festival date, and distinguishes itself from asterwise_get_panchanga_calendar and asterwise_get_muhurta. This provides clear usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Asterwise tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?