AstroWay Vedic astrology

Hindu calendar: festivals for a year and place

astroway_vedic_calendar_festivals

Read-onlyIdempotent

About 55 pan-Indian festivals dated for the place: Makar Sankranti, Maha Shivaratri, Holika Dahan and Holi, Ugadi, Rama Navami, Hanuman Jayanti, Akshaya Tritiya, Guru Purnima, Raksha Bandhan, Janmashtami, Ganesh Chaturthi, Navratri, Dussehra, Karva Chauth, Dhanteras, Diwali, Govardhan Puja, Bhai Dooj, Chhath, Onam, Puthandu, Vishu, Pohela Boishakh and more.

[Group: Vedic] [Endpoint: POST /v1/vedic/calendar/festivals] [Required: year, latitude, longitude] [Cost: 100 credits (Tier 4)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_vedic_calendar_festivals"
  }
}

Input Schema

Name	Required	Description
`year`	Yes	Gregorian year, 1900 to 2100. Entries are those whose date falls in this year.
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`ayanamsa`	No	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`latitude`	Yes	Latitude in decimal degrees, north positive. Between -66 and 66: further out the Sun does not rise on some days and a Hindu day has no start.
`timezone`	No	IANA zone name such as Asia/Kolkata, America/New_York or Europe/Kyiv, or auto (default) to look it up from the coordinates. Resolved day by day: each day is read on the offset that zone kept that day, so summer time is followed.
`festivals`	No	Only these festival ids. All when omitted.
`longitude`	Yes	Longitude in decimal degrees, east positive.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`tradition`	No	Whose reckoning decides the day where they differ (Rama Navami, Janmashtami). smarta (default): the tithi at the rite's kala, as Dharmasindhu gives it; vaishnava: the ISKCON rule, the tithi at sunrise unmixed with the one before.
`ayanamsaId`	No
`timezoneOffset`	No	A fixed offset in hours instead of a zone, for the whole year. Ignored when timezone is sent.

Output Schema

Name	Required	Description	Default
`year`	No
`count`	No
`place`	No
`festivals`	No
`tradition`	No
`conventions`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds the notable extras: a fixed catalogue size (~55), that dates are computed for the supplied place, and the Tier-4 price of 100 credits. It does not disclose that omitting the festivals filter returns all of them, or that ayanamsa/tradition can shift dates.

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?

Front-loaded with the core statement of what is returned, and the bracketed metadata lines are easy to scan. The 24-name enumeration is long but functions as keyword surface for user phrasing (e.g. 'when is Karva Chauth'), so it mostly earns its space; a few examples plus 'and more' would have been tighter.

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

Completeness3/5

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

With 11 parameters, full annotations and an output schema, the description covers purpose, scope and cost adequately, and return values need no explanation. What is missing is routing context — why pick this over the vrats, regional_date or ics siblings — which matters given how many calendar tools exist here.

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

Parameters3/5

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

Schema description coverage is 91%, so the schema already explains year range, latitude limits, timezone resolution, tradition and ayanamsa. The description only restates the three required parameters and lists festival names that already appear as an enum; it adds no default or interaction semantics beyond the schema.

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

Purpose4/5

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

States the resource concretely — roughly 55 pan-Indian festivals dated for a given place and year — and the enumeration of names (Diwali, Karva Chauth, Onam, Puthandu...) makes the content unmistakable. It never names a sibling, however, so the boundary with astroway_vedic_calendar_vrats, _months, _regional_date or _ics is left implicit.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance and no mention of the obvious alternatives in the same family (vrats for fasting days, ics for calendar export, regional_date for a single day). The only usage-relevant facts are the required inputs and the 100-credit cost, both restated from structured metadata.

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

All AstroWay Vedic astrology 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?