Skip to main content
Glama

Supastro

Get the panchang for a city

get_panchang
Read-onlyIdempotent

Calculates the Hindu panchang for one day in one city: weekday, tithi, nakshatra, yoga and karana with the time each ends, Moon sign, sunrise, sunset, moonrise and moonset, lunar month, Rahu Kaal and the other daily time windows, and the day's observances. Use it when someone asks for today's panchang, tithi, nakshatra, Rahu Kaal or sunrise for a place. Times are in the city's own time zone. Covers today by default, or another date.

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

Input Schema

NameRequiredDescriptionDefault
dateNoOptional. The day as YYYY-MM-DD. Defaults to today in that city. Convert the person's own wording to this form; if an all-number date could be read two ways, ask which number is the day.
placeYesCity and country, for example "Pune, India".
latitudeNoOptional. Latitude of the city in decimal degrees, north positive. Give it only together with longitude, when the user supplied coordinates or the place could not be found by name.
longitudeNoOptional. Longitude of the city in decimal degrees, east positive. Give it only together with latitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful behavioural facts beyond that: "Times are in the city's own time zone" and that the tool covers today by default or another date. It does not discuss failed place resolution or result precision, but the main behavioural surprises are disclosed.

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?

Front-loaded with the core purpose, then outputs, then usage triggers—a sensible order. It is dense but nearly all of the enumeration earns its place for query matching; the only mild waste is repeating "Rahu Kaal" and "sunrise" in the usage sentence after listing them among outputs.

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 no output schema, the description correctly compensates by listing what is returned (weekday, tithi, nakshatra, yoga, karana with end times, moon sign, rise/set times, lunar month, Rahu Kaal, observances). Combined with time-zone and date-default disclosure, an agent has what it needs to call this correctly; only error/failure behaviour 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%, including date format, defaulting and the latitude/longitude pairing rule, so the schema already carries the parameter burden. The description adds little param-level detail beyond reiterating the today-default and the time-zone of returned data; 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 and resource ("Calculates the Hindu panchang for one day in one city") and then enumerates the exact outputs—tithi, nakshatra, yoga, karana, Rahu Kaal, sunrise/sunset—so an agent can match a user question to this tool without opening the schema. It is clearly distinguishable from neighbouring chart/transit tools by its single-day, single-city scope.

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?

Gives an explicit trigger set: "Use it when someone asks for today's panchang, tithi, nakshatra, Rahu Kaal or sunrise for a place." It also clarifies the default (today) and that another date is allowed. It does not name an alternative for adjacent daily-timing topics (e.g. choghadiya/other daily time windows are mentioned only in passing), so there is a small gap on when-not-to-use.

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