Skip to main content
Glama

HinduCalendar — panchang, festivals & muhurta

get_festival_dates

Read-only
Exact dates of major Hindu festivals for any year, computed live by the
same engine the HinduCalendar app uses — never guess a festival date,
always use this.

Covers the tithi-anchored festivals (Diwali, Holi, Krishna Janmashtami,
Ganesh Chaturthi, Rama Navami, Maha Shivaratri, Raksha Bandhan, Dhanteras,
Karva Chauth, Chhath, Vasant Panchami, Gudi Padwa, Akshaya Tritiya, the
purnimas, Navratri from Ghatasthapana through Vijayadashami) *and* the ones
no tithi rule can express: solar ingresses (Makar Sankranti — also Pongal,
Uttarayan, Maghi; Mesha Sankranti — also Vishu, Baisakhi, Puthandu),
nakshatra-dated observances (Onam, the Jyeshtha Gauri triad), weekday
series (Shravan Somwar, Mangala Gauri), and the Puri Jagannath sequence
(Snana Yatra, Rath Yatra, Hera Panchami, Bahuda Yatra, Suna Besha,
Niladri Bije).

Every result carries `date` and a plain-language `rule` saying how that
date is fixed, usually with a `why` explaining it, plus regions,
traditions, cluster and related festivals where they are recorded.
Tithi-anchored festivals also carry `masa`/`paksha`/`tithi`; solar and
nakshatra ones do not, because they have none.

Two results are not single days:
  • one that recurs within the year (Shravan Somwar is four or five
    Mondays) carries `dates` with every occurrence — `date` is the first;
  • a multi-day observance (Ganeshotsav, Navratri) carries `end_date`
    and `days`.

Example questions: "when is Diwali in 2027?", "what date was Holi in
1962?", "list all festivals in 2026", "when is Onam?", "which Mondays are
Shravan Somwar this year?".

Args:
    year:      Gregorian year.
    festival:  Optional name filter — fuzzy, and matches popular and
               regional aliases plus Devanagari ("Diwali", "Dussehra",
               "Rakhi", "Pongal", "Vishu", "दिवाली"). A sequence name
               ("Navratri", "Ganeshotsav", "Rath Yatra") returns every
               festival in that sequence.
    lat, lon, tz_offset_hours:
               Location (default Ujjain, the canonical reference).
               Festival days can shift by location; for a user's city
               pass their coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNo
lonNo
yearYes
festivalNo
tz_offset_hoursNo

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it explains that dates are computed live, describes return fields (date, rule, why, regions, etc.), and documents special cases like multi-day observances carrying dates/end_date/days. It also clarifies which festivals carry masa/paksha/tithi and which do not.

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

Conciseness5/5

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

The description is long but each section earns its place: overview, festival coverage, output format, special cases, examples, and parameter details. It is front-loaded with the core statement and organized with bullets for readability.

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?

Despite lacking an output schema, the description thoroughly covers return values and edge cases, making it complete for a complex festival-date tool. It also provides examples and location sensitivity.

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

Parameters5/5

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

The Args section provides detailed semantics not in the schema: festival supports fuzzy matching, aliases, Devanagari, and sequence names; lat/lon/tz affect dates with Ujjain default. This fully compensates for the schema's 0% description coverage.

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 opens with 'Exact dates of major Hindu festivals for any year' and enumerates specific festivals, making the resource and scope unambiguous. It clearly distinguishes from siblings by name and function—festival dates versus birth details, muhurat, and panchang.

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

Usage Guidelines4/5

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

It instructs 'never guess a festival date, always use this' and provides example questions like 'when is Diwali in 2027?' and 'list all festivals in 2026'. It does not explicitly name alternative tools for other needs, but the scope is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation4/5

Each tool targets a distinct aspect of the Hindu calendar (birth details, festivals, muhurat windows, moment-specific muhurta, panchang). However, get_muhurta and get_muhurat_windows have overlapping names and could be initially confused, though the descriptions clearly separate single-day versus multi-day windows.

Naming Consistency4/5

All tools use the consistent 'get_' prefix with descriptive nouns (birth_details, festival_dates, muhurat_windows, muhurta, panchang). Minor inconsistency: 'muhurat_windows' uses plural and modifier while 'muhurta' is singular, but overall the pattern is recognizable and predictable.

Tool Count5/5

Five tools is well-scoped for a specialized Hindu calendar server. Each tool covers a distinct major feature (birth chart, festivals, muhurat windows, daily muhurta, panchang), and none feel redundant or excessive.

Completeness5/5

The tool surface covers the core needs of a Hindu calendar app: panchang details, festival dates (including complex tithi/solar rules), muhurta for specific moments and broad windows, and birth details (nakshatra/rashi). There are no obvious gaps for the stated purpose; the reference to an external server for Hindu-to-Gregorian conversion is a sensible boundary rather than a deficiency.

Resources