Skip to main content
Glama

Vedha360

Pañcāṅga for a date and place

get_panchang
Read-onlyIdempotent

The Hindu calendar day (pañcāṅga) for a date at a place: vāra (weekday), tithi (lunar day) and when it ends, pakṣa, nakṣatra and when it ends, sunrise, sunset, moonrise, moonset and the day's observances. Times are ISO-8601 in the place's time zone.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_panchang"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA time zone, e.g. 'Asia/Kolkata'Asia/Kolkata
latYesLatitude of the place
lonYesLongitude of the place
dateNoYYYY-MM-DD; default today at the place

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds genuine context beyond them: that times are ISO-8601 rendered in the place's time zone, and that some fields are paired with end times. It does not cover failure modes (out-of-range lat/lon, invalid tz) but that is minor for a read-only computation.

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?

Two sentences, with the resource and scope front-loaded before the field enumeration. The long list of returned elements is dense but each item is substantive; a small amount of parenthetical glossing could be trimmed, but nothing is wasted.

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?

With an output schema present, the description need not spell out return structure, yet it still summarizes the payload and the time format. Combined with full schema coverage and rich annotations, an agent has nearly everything needed; only error/edge behavior for invalid coordinates is unaddressed.

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 latitude, longitude, tz and date are already fully documented, including the 'default today at the place' behavior. The description adds only the framing that results are localized to the place's time zone; it introduces no syntax or constraints beyond the schema. Baseline 3 applies.

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?

States a specific verb-resource pair: it returns the Hindu calendar day (pañcāṅga) for a date at a place. It then enumerates the exact contents (vāra, tithi with end time, pakṣa, nakṣatra with end time, sunrise/sunset, moonrise/moonset, observances), which is far more specific than the title alone and cannot be confused with any sibling scripture/story/temple tool.

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 implied by 'for a date at a place' and the coordinate inputs, so an agent can infer this is the almanac lookup tool. There is no explicit when-to-use/when-not-to-use framing and no named alternative, though the sibling set makes the role reasonably unambiguous.

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