A
licenseA
qualityA
maintenanceHosted Streamable HTTP MCP server for Vedic astrology: panchang, kundali (birth chart), matchmaking, dashas, doshas, muhurta and 16 tools computed by a precision astronomy engine.
Last updated
17
51
MIT
HinduCalendar — panchang, festivals & muhurta
Server Details
Daily panchang, festivals, muhurta and birth details, identical to the HinduCalendar Android app.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.7/5.0
Tool DescriptionsA
Average 4.7/5 across 4 of 4 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool addresses a distinct aspect of Hindu calendrical computation: birth details, festival dates, current muhurta, and full daily panchang. There is no overlap in purpose or output, so an agent can easily select the right tool.
Naming Consistency5/5
All tool names follow the consistent 'get_' + noun pattern in snake_case (get_birth_details, get_festival_dates, get_muhurta, get_panchang). This is uniform and predictable.
Tool Count5/5
Four tools is a well-scoped set for a Hindu calendar server, covering core needs without bloat. Each tool has a clear function and the count feels appropriate for the domain.
Completeness4/5
The set covers the primary use cases: daily panchang, festivals, muhurta, and birth details. Minor gaps exist, such as no tool to search muhurta for a date range or convert Hindu dates to Gregorian, but the latter is intentionally delegated to another server and the core surface is strong.
Available Tools
4 toolsget_birth_detailsARead-onlyInspect
Return birth star (nakshatra), birth name syllable (naam akshar / pada),
Chandra rashi (Moon sign), and Lagna rashi (ascendant sign) for a child
born at the given time and location — all from the app's own engine, so
they match the HinduCalendar app's kundali exactly.
Args:
time: ISO 8601 datetime of birth (e.g. "2025-08-15T10:30:00Z").
Include timezone offset if known (e.g. "2025-08-15T10:30:00+05:30").
lat: Latitude of birth place in decimal degrees (e.g. 28.6139 for Delhi).
lon: Longitude of birth place in decimal degrees (e.g. 77.2090 for Delhi).
ayanamsa: "Lahiri" (Vedic sidereal, default) or "Sayan" (tropical).
Returns:
Dict with:
- time (ISO)
- ayanamsa
- nakshatra: { index (1–27), name }
- pada: { index (1–4), overall_index (1–108), naam_akshar (birth name syllable) }
- chandra_rashi: { index (1–12), name } ← Moon sign
- lagna_rashi: { index (1–12), name } ← Ascendant sign
Plus a rendered South Indian kundali chart (PNG image).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lat | Yes | ||
| lon | Yes | ||
| time | Yes | ||
| ayanamsa | No | Lahiri |
Tool Definition Quality
A4.8/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only and closed world. The description adds significant behavioral context: it uses the app's own engine for consistency, and it returns both structured data and a rendered PNG chart. It also details the exact return structure, providing transparency beyond annotations. No contradiction.
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 well-structured with a clear purpose statement, an Args section with bullet-style details, and a Returns section listing all output fields. It's detailed but every part serves a purpose, with the main verb and resource 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?
Given the absence of an output schema, the description enumerates all return fields (nakshatra, pada, chandra_rashi, lagna_rashi) and mentions the rendered chart. It also covers all required inputs with examples. This makes the description complete for an agent to invoke and interpret results.
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 schema has no property descriptions (0% coverage), but the description compensates fully: each parameter is explained with format, units, and examples (e.g., ISO 8601 with timezone for time, decimal degrees for lat/lon, and two allowed values for ayanamsa with default). This adds substantial meaning beyond the bare schema.
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 explicitly states the tool returns birth star, name syllable, Moon sign, and ascendant sign for a given birth time and location, and emphasizes it matches the app's kundali. This clear verb+resource+scope distinguishes it from sibling tools (festivals, muhurta, 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?
The description clearly indicates the tool is for obtaining birth details for a child, with input parameters and a note that results match the app's engine. It doesn't explicitly mention when not to use it or name alternatives, but given the distinct purpose and sibling names, the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_festival_datesARead-onlyInspect
Exact dates of major Hindu festivals for any year, computed live from the
tithi rules by the same engine the HinduCalendar app uses — never guess a
festival date, always use this.
Covers: Diwali (Deepavali), Holi, Navaratri endpoints (Mahanavami,
Vijayadashami), Krishna Janmashtami, Ganesh Chaturthi, Rama Navami,
Maha Shivaratri, Raksha Bandhan, Dhanteras, Chhath, Vasant Panchami,
Gudi Padwa, Akshaya Tritiya, Buddha Purnima, Guru Purnima, and more.
Each result carries its panchang rule (masa + paksha + tithi).
Example questions: "when is Diwali in 2027?", "what date was Holi in
1962?", "list all festivals in 2026".
Args:
year: Gregorian year.
festival: Optional name filter (e.g. "Diwali", "holi",
"janmashtami") — fuzzy matched.
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | ||
| lon | No | ||
| year | Yes | ||
| festival | No | ||
| tz_offset_hours | No |
Tool Definition Quality
A4.6/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark it read-only with openWorldHint false. The description adds valuable behavioral context: live computation from tithi rules, fuzzy matching, location sensitivity, and per-result panchang rule. It does not fully describe return format or edge cases, but the additional context is substantial and consistent with annotations.
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 well-structured with an intro, coverage list, example questions, and a concise args section. Every sentence adds distinct value with no redundancy.
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?
For a tool with 5 parameters and no output schema, the description is nearly self-sufficient: it covers purpose, scope, examples, parameter meanings and defaults, and result characteristics. The only minor omission is a detailed output schema, but that is not required for effective usage.
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?
Schema description coverage is 0%, so the description carries full burden. It explains year, festival (fuzzy matching), lat/lon/tz_offset with Ujjain default and why location matters, far exceeding the bare schema.
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 computes exact dates of major Hindu festivals from tithi rules, gives an explicit coverage list, and includes example questions. This specific verb+resource framing distinguishes it from sibling tools like panchang and muhurta.
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 gives explicit guidance: 'never guess a festival date, always use this' and explains when to pass user coordinates. It does not explicitly name alternatives or exclusions, but the sibling tool names and the focused scope imply when each should be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_muhurtaARead-onlyInspect
Return the muhurta details active at a given time and location, exactly
as the HinduCalendar app computes them:
- 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)
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.
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".
Returns:
Dict with sunrise, sunset, current_lagna, current_choghadiya,
current_hora, and ongoing_muhurtas.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lat | Yes | ||
| lon | Yes | ||
| lang | No | en | |
| time | Yes |
Tool Definition Quality
A4.6/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavioral detail beyond the readOnlyHint annotation: it states calculations follow the HinduCalendar app, choghadiya/hora are pure rise/set arithmetic, and it notes UTC assumption without timezone. It does not contradict annotations and offers engine-level transparency.
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 well-organized: a summary line, a bulleted list of outputs, a note on calculation source, and an Args/Returns breakdown. No redundant text; each element serves a purpose and the structure is front-loaded with the core purpose.
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?
Without an output schema, the description provides a detailed Returns section listing all returned fields. It also explains the computational source and default timezone behavior, making the tool's behavior fully understandable for an agent.
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?
Schema coverage is 0%, but the description fully documents all 4 parameters: time with ISO format and example, lat/lon with units, and lang with default and allowed values. This completely compensates for the lack of schema 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 clearly states the tool returns muhurta details active at a given time and location, enumerating specific outputs (lagna, choghadiya, hora, special muhurtas). This verb+resource+scope construction distinguishes it from siblings like get_panchang, which would provide a broader or different set of details.
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?
The description indicates use for obtaining active muhurta details at a specified time/location, and lists required parameters. It does not explicitly mention alternatives or when not to use, but the context is clear enough for selection among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_panchangARead-onlyInspect
Full daily panchang for a date and place — computed by the same
panchang-core engine the HinduCalendar Android app ships, so the values
are identical to the app (not an approximation).
Returns the five limbs at sunrise (tithi, nakshatra, yoga, karana, vaar)
each with its END TIME, paksha, lunar month in both amavasyant and
purnimant conventions (with adhik maas flag), Vikram/Shaka/Kali/Gujarati
samvat years, samvatsara names, ritu (season), ayana (Uttarayan/
Dakshinayan), sun/moon rashi with next-transit time, and sunrise/sunset/
moonrise/moonset.
This is also the Gregorian→Hindu date converter: the masa + paksha +
tithi + samvat fields ARE the Hindu date. (For Hindu→Gregorian, use the
Kaalshodh MCP server's find_matching_dates.)
Example questions: "what is the tithi today in Delhi?", "when does
Ekadashi end tomorrow?", "what is today's date in Vikram Samvat?",
"which Hindu month is it?".
Args:
date: Gregorian date, YYYY-MM-DD. Default location is Ujjain;
pass lat/lon/tz for other places.
lat, lon: Location in decimal degrees.
tz: IANA timezone name ("Asia/Kolkata") or a numeric UTC
offset in hours ("5.5").
ayanamsa: "Lahiri" (default) or "Sayan".
lang: Language for names — "en", "hi", and the app languages
(mr, gu, bn, ta, te, kn, ml, sa) plus "en-iast".
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tz | No | Asia/Kolkata | |
| lat | No | ||
| lon | No | ||
| date | Yes | ||
| lang | No | en | |
| ayanamsa | No | Lahiri |
Tool Definition Quality
A4.8/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With readOnlyHint=true already present, the description adds meaningful behavioral context: values are computed by the same engine as the HinduCalendar app (not an approximation), all limbs include their END TIME, and the default location is Ujjain with timezone/ayanamsa/language options. It also clarifies that the output constitutes a complete Hindu date conversion, going well beyond the annotation baseline.
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 densely packed with irreplaceable information. It front-loads the core purpose, then uses a structured list of outputs, a clear conversion note, example questions, and a labeled Args section. No sentence is wasted; each adds unique value for such a complex tool.
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 high complexity (six parameters, no output schema), the description is remarkably complete. It details every return category, provides default behavior, explains parameter usage, and gives real-world example queries. The absence of an output schema makes this thoroughness essential, and it fully delivers.
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 provides only types and defaults (0% description coverage), so the description carries the full burden. It fully compensates by explaining the date format (YYYY-MM-DD), the meaning of lat/lon and default Ujjain location, tz as IANA name or numeric offset, ayanamsa choices (Lahiri/Sayan), and lang options including app languages. Every parameter receives meaningful semantic explanation.
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 clear action: 'Full daily panchang for a date and place' and explicitly enumerates all returned components (tithi, nakshatra, yoga, karana, vaar, samvat years, etc.). It differentiates itself from siblings by focusing on daily panchang and also identifies a secondary role as a Gregorian→Hindu date converter, making its purpose unmistakable.
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?
The description provides clear usage context through example questions and explicitly points to find_matching_dates on the Kaalshodh server for the reverse conversion (Hindu→Gregorian), naming an alternative. It does not explicitly state when to avoid this tool relative to sibling tools, but the purpose is so distinct that the context is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityAmaintenanceTelugu Panchangam for AI assistants: daily panchangam, muhurta windows, tarabalam, festivals, eclipses, gochara and planetary positions for any city, computed in three classical systems (Drik Ganita, Surya Siddhanta, Vakya). 17 tools; runs via uvx mcp-server-panchangam.Last updated17MIT
- Alicense-qualityDmaintenanceProvides Chinese traditional calendar functions including BaZi calculation, solar-lunar calendar conversion, Huangli almanac queries, daily fortune readings, 24 solar terms, and Wu Xing (Five Elements) analysis.Last updatedMIT
- AlicenseAqualityBmaintenanceProvides traditional Chinese lunar calendar information including auspicious date checking, BaZi (八字) Four Pillars analysis, festival data, moon phases, zodiac compatibility, and calendar conversions based on Chinese cultural traditions.Last updated202MIT