Namaste America

get_festival_dates

Upcoming Indian & South-Asian festival dates for planning in the USA.

With no `query`, returns the next `limit` festivals soonest-first. With a `query` (e.g. "Diwali",
"when is holi"), returns the single soonest matching festival. Each item has name, date (ISO),
days_until, emoji and a greeting. IMPORTANT: many Hindu/Sikh/Jain/Muslim festivals follow lunar
calendars, so these dates are best-effort — always tell the user to confirm the exact date with
their local temple, gurdwara, mosque or a panchang. Returns {'results': [...], 'note': ...}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedJul 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that dates are best-effort due to lunar calendars and advises users to confirm with local religious institutions. It also mentions the return format (name, date, days_until, emoji, greeting) and a top-level note.

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 front-loaded with the purpose, followed by behavior and a warning. It is reasonably concise with three sentences plus a caveat. Every sentence adds value, though the warning could be shortened slightly.

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

Completeness5/5

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

Given the tool's simplicity (2 parameters, no required params, output schema exists), the description adequately covers parameter behavior, return format, and an important caveat about date accuracy. It feels complete for an agent to understand and invoke the tool correctly.

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?

Schema coverage is 0%, so the description must compensate. It explains the behavior of both parameters: limit defaults to 6, query defaults to empty, and describes how query affects results. It adds meaning beyond the schema by linking parameters to tool behavior.

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?

The description clearly states it returns upcoming Indian/South-Asian festival dates for planning in the USA. It distinguishes behavior with and without a query parameter. However, it does not explicitly differentiate from sibling tools like get_indian_events, which may overlap in purpose.

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

Usage Guidelines3/5

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

The description explains when to use the tool with no query (returns next limit festivals) and with a query (returns single soonest matching). It provides context for both use cases but does not mention when not to use it or suggest alternatives among siblings.

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

All Namaste America tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.