Skip to main content
Glama

AstroLogics

Daily panchang

get_panchang
Read-onlyIdempotent

Get the Vedic panchang for a date and place: tithi, nakshatra, yoga, karana, vara and Rahu Kaal.

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": {
      "date": "<date>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_panchang"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate, YYYY-MM-DD.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.
latitudeYesLatitude in decimal degrees.
longitudeYesLongitude in decimal degrees.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.",
      +  "enum": [
      +    "en",
      +    "hi"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description's only added behavioral content is the list of returned panchang elements, which is genuinely useful given there is no output schema, but it says nothing about timezone handling or whether Rahu Kaal is returned as a 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 with the resource and the returned fields in one pass, and no filler or redundancy. Nothing could be cut without losing information.

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 read-only, idempotent lookup with 100% parameter coverage and a clear enumeration of outputs, this is close to complete. The residual gap is that nothing explains how date plus coordinates are combined (local timezone of the computed panchang), which matters for a day-boundary-sensitive almanac.

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 date, latitude, longitude and the en/hi language switch are all documented in the schema itself. The description adds only the loose phrase "for a date and place", which restates the schema rather than adding format or precision guidance. Baseline 3 applies when the schema carries the load.

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 the Vedic panchang for a date and place") and enumerates exactly which elements come back: tithi, nakshatra, yoga, karana, vara, Rahu Kaal. That is enough to tell it apart from sibling calculators like get_choghadiya or find_muhurat in most cases, but no sibling is named and the overlap with other time-division tools is left implicit.

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 only implied by the purpose: an agent can infer this is the tool for a daily almanac lookup for a given date and location. There is no statement of when to prefer this over get_choghadiya, find_muhurat, or get_festival_calendar, and no note on prerequisites such as needing coordinates.

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