Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_hindu_festivals

Retrieve Hindu festival dates for a specified month and year, with optional English or Hindi output, to support panchang and astrology-related queries.

Instructions

Execute hindu_festivals AstroChalit API to get festivals for a given month and year

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>",
      "month": "<month>"
    },
    "name": "get_hindu_festivals"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesYear (e.g. 2024 to 2040)
monthYesMonth (1-12)
languageNoLanguage: 'en' for English or 'hi' for Hindi. Default: 'en'en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing beyond the purpose. It does not say what the response contains (festival names, dates, tithi/nakshatra associations), whether results can be empty for a month, whether there is pagination, or any auth/rate-limit behavior. The 'get' phrasing weakly implies a read-only operation but this is not stated.

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?

A single short sentence with the core purpose front-loaded and no filler sentences. The 'Execute ... AstroChalit API' clause is redundant internal detail that could be dropped, but the overall size is appropriate.

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?

For a simple three-parameter read tool with a fully documented schema, the description is minimally adequate. However, with no output schema and no annotations, the agent is left guessing at the returned structure and at empty-result behavior, which the description should have covered.

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 100%, so the schema already documents the year range, month 1-12, and the 'en'/'hi' language enum with its default. The description only restates the month/year scoping and adds no format or edge-case detail (e.g., behavior for the Hindi locale, valid year bounds) 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 a specific verb and resource ('get festivals') plus the scoping dimensions ('given month and year'). It is clearly distinct from the sibling tools, which are all chart/dasha/koot calculations, so an agent can tell it apart without opening the schema. The only noise is the implementation phrasing 'Execute hindu_festivals AstroChalit API', which restates the tool name.

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 month-and-year scoping implies the retrieval use case, but there is no explicit when-to-use, when-not-to-use, or routing guidance relative to alternatives. Usage is inferable from the name and parameters rather than stated.

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

Deploy Server

Other Tools