Skip to main content
Glama

AstroLogics

Hindu festival and vrat dates

get_festival_calendar
Read-onlyIdempotent

List Hindu festival, vrat, Ekadashi, Sankranti and Shraddha dates in a date range (covers the 2026 calendar; dates as observed in India).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_festival_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date, YYYY-MM-DD. Defaults to 60 days after the start.
fromNoStart date, YYYY-MM-DD. Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, closed-world lookup, so the bar for behavioral disclosure is lower. The description adds useful context about calendar coverage and Indian observance, but says nothing about return ordering, timezone handling, or what happens outside the 2026 window.

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?

A single front-loaded sentence identifies the resource and the range constraint, with the coverage caveats compactly placed in parentheses. Every phrase earns its place, with no redundant restatement of the tool name or annotations.

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?

For a two-parameter read-only lookup with full schema coverage and no output schema, the description covers purpose, range, and domain limitations adequately. It could be stronger by noting return ordering or the behavior outside the 2026 coverage window, but nothing essential to calling it correctly is missing.

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 coverage is 100%, and the schema itself documents both 'from' and 'to' with YYYY-MM-DD patterns and default behavior. The description only restates that the tool operates on a date range, adding no format or edge-case detail beyond the schema, so the baseline of 3 is appropriate.

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 gives a specific verb, 'List', and a precise resource: Hindu festival, vrat, Ekadashi, Sankranti and Shraddha dates within a date range. It also states scope limits (2026 calendar, dates as observed in India), which helps distinguish it from broader sibling tools like get_panchang, though no sibling is named explicitly.

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?

Usage is implied by the date-range framing and the note that it covers the 2026 calendar, which signals a coverage boundary. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternative such as get_panchang or find_muhurat for overlapping needs.

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.

Resources