Skip to main content
Glama

Kundlit Vedic Astrology

by com.kundlit

Hindu festival & vrat dates for a year

get_year_events
Read-onlyIdempotent

Returns dated Hindu calendar events for a whole year at one city. category='festival' lists every festival and vrat that year (Holi, Diwali, Navratri, Shivratri and the rest); the other categories list every ekadashi, purnima, amavasya or sankranti date. Each row is the exact local date and the event name, plus a one-line significance on shorter lists. Use this for 'when is X this year' and 'list all ekadashi dates' questions. For the detail of a single day (tithi, sunrise, rahu kaal) call get_panchang with that date; for eclipses call get_eclipses. Read-only deterministic computation (Swiss Ephemeris, Lahiri ayanamsa), served from a shared cache -- a cold or expired entry recomputes and can take ~30s; no writes, no auth, at least 30 requests/min/IP per server instance, plus a shared engine budget of at least 60/min/IP across all engine-backed tools. Constraints: the year must be within two years either side of the current year, and results are computed for the nearest of 50 supported cities (a location_note names it when the snap is far); long lists are capped at 80 rows, so pass month to page through them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesGregorian calendar year as a number, e.g. 2026. Only the current year plus or minus two is supported; anything else is rejected.
monthNoRestrict the result to a single Gregorian month, 1 = January to 12 = December. Omit for the whole year. Use it when a year-wide list came back truncated.
placeNoCity as free text, e.g. "Jaipur" or "Chennai, India". Omit to use Delhi. Any input is snapped to the nearest of 50 supported cities, since tithi-based dates can differ by a day between distant longitudes.
categoryYes"festival" returns every event of the year; "ekadashi", "purnima", "amavasya" and "sankranti" each narrow the list to that lunar/solar family only.

TDQS

A4.9/5.0
Behavior5/5

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

Discloses read-only deterministic computation, cache behavior with ~30s cold start, no writes, no auth, and specific rate limits per IP per instance and shared engine budget. This adds beyond annotations which only state readOnlyHint, idempotentHint, and destructiveHint.

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 comprehensive but slightly long. Every sentence earns its place, covering purpose, usage, behavior, and parameters. Could be marginally condensed, but structure is logical and front-loaded.

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 no output schema, the description explains return format (date, event name, significance) and pagination via month parameter. Covers constraints, rate limits, caching, and city snapping, making it complete for a complex tool.

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?

With 100% schema description coverage, the description adds context on month usage for paging, place snapping logic, category narrowing, and year constraints. It explains why place is snapped and how to handle truncated results.

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 clearly states the tool returns dated Hindu calendar events for a whole year at one city, with specific event categories. It distinguishes from sibling tools like get_panchang and get_eclipses by contrasting use cases.

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

Usage Guidelines5/5

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

Explicitly provides when to use (e.g., 'when is X this year', 'list all ekadashi dates') and when not to use (e.g., for single day detail call get_panchang, for eclipses call get_eclipses). Also specifies constraints like year range and 80-row limit with month paging.

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

All Kundlit Vedic Astrology toolsInspect
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.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct astrological calculation or domain: dosha checks, birth charts, compatibility, muhurta, panchang, numerology, transits, and Jaimini layer. Even similar tools (e.g., get_panchang vs get_muhurta_timings) are explicitly differentiated in their descriptions, and cross-references tell the agent which to use for which question.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: 'get_' for data retrieval and 'check_' for yes/no dosha assessments. No camelCase or mixed conventions. The naming is predictable and readable.

Tool Count4/5

At 17 tools, the set is slightly above the ideal 15-tool ceiling, but it is well-scoped for the breadth of Vedic astrology: each tool earns its place covering a distinct sub-domain. The count feels justified rather than bloated.

Completeness5/5

The surface covers the full lifecycle of a birth chart (details, full kundli, dasha), doshas (manglik, kaal sarp, sade sati), compatibility (kundli match), event planning (muhurta, panchang, year events, eclipses), numerology (personal, mobile, name), and advanced layers (upapada, transits). No obvious gaps or dead ends.

Resources