HinduCalendar — panchang, festivals & muhurta

get_muhurta

Read-only

Muhurta for a moment and place, exactly as the HinduCalendar app computes
it — and, with full_day=True, the whole day's grid.

By default returns only what is ACTIVE at the instant given:
  - Current lagna (ascendant sign active at that moment)
  - Current choghadiya (day or night slot)
  - Current hora (planetary hour)
  - Any ongoing special muhurtas (Rahu Kalam, Yama Ghanta, Guli Kalam,
    Abhijit, Dur Muhurt, Pradosh, Varjyam, Panchak, Gandmool)

Set full_day=True to also get every window of the panchang day (sunrise to
next sunrise) containing that instant — the complete choghadiya and hora
grids (day and night), all lagna periods, and every special muhurta with
its start and end. Use it for "when is Rahu Kalam today?", "list today's
choghadiya", "when is Abhijit muhurat?" — questions the instant-only view
cannot answer without guessing the time.

Sunrise/sunset, lagna transitions and every special muhurta come from
panchang-core (the app's engine); choghadiya/hora are pure rise/set
arithmetic driven by the engine's times and weekday.

For multi-day observance periods and auspicious-yoga windows (Vivaah
muhurat, Sarvarth Siddhi, Pitru Paksha, Chaturmas, Panchak…) use
get_muhurat_windows instead — this tool covers a single day.

Args:
    time:     ISO 8601 datetime (e.g. "2025-08-15T10:30:00+05:30"). If no
              timezone is given, UTC is assumed.
    lat:      Latitude in decimal degrees.
    lon:      Longitude in decimal degrees.
    lang:     Language for names — "en" (default) or "hi".
    full_day: Include the whole day's grids, not just what is active now.

Returns:
    Dict with sunrise, sunset, current_lagna, current_choghadiya,
    current_hora, and ongoing_muhurtas — plus choghadiya, hora, lagna and
    muhurtas when full_day is set.

Input Schema

TableJSON Schema

Name	Required	Default
`lat`	Yes
`lon`	Yes
`lang`	No	en
`time`	Yes
`full_day`	No

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint, the description explains the computation source (panchang-core), the day boundary (sunrise to next sunrise), and exactly what the default vs. full_day returns include. It also specifies the behavior for timezone-less input, adding context not available from annotations.

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 well-structured with clear sections (summary, default returns, full_day explanation, source note, sibling pointer, Args, Returns) and front-loaded with the key purpose. It is somewhat lengthy, and the Returns section partially duplicates the earlier bullet list, but every section adds needed detail.

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 has 5 parameters and no output schema, the description is remarkably complete. It documents all parameters, the full return structure for both default and full_day modes, and relates to a sibling tool. No gaps remain for an agent to invoke it correctly.

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 input schema has 0% description coverage, but the Args section provides full semantics: ISO 8601 format and UTC default for time, decimal degrees for lat/lon, language options for lang, and an explanation of full_day behavior. This fully compensates for the schema's lack of descriptions.

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 a specific statement: 'Muhurta for a moment and place, exactly as the HinduCalendar app computes it' and clearly distinguishes from get_muhurat_windows by noting it covers a single day. It also enumerates the exact output categories, leaving no doubt about what the tool does.

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?

The description explicitly tells when to use full_day=True with concrete example questions ('when is Rahu Kalam today?') and when to use get_muhurat_windows for multi-day periods. This provides clear decision guidance relative to sibling tools.

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

All HinduCalendar — panchang, festivals & muhurta 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.

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

Need Help?