Skip to main content
Glama

Cosmic Chemistry

Panchang for a day (Hindu calendar)

daily_panchang
Read-onlyIdempotent

Use this when someone asks for today’s panchang or the Hindu calendar for a place: the tithi, nakshatra, yoga, karana, Rahu kaal (rahu kalam), Yamaganda, Gulika, Abhijit muhurat, choghadiya, sunrise and sunset, or which festival or vrat falls today ("aaj ka panchang", "what is today’s tithi", "Rahu kaal today in Pune", "is today Ekadashi", "good time to start today"). Also answers for another date. Needs no birth details. Send the town if the person has said it; without one the answer is for New Delhi. Do not use for a person’s birth chart or birth star.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "daily_panchang"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe date wanted, as YYYY-MM-DD. Leave out for today at that place.
placeNoTown or city, with region or country if known, e.g. "Pune, India" or "Austin, Texas".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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 openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts the annotations cannot convey: no birth details are needed, and absent a place the result defaults to New Delhi. It stops short of describing output shape or any rate/limit behavior, so it is not a full 5.

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 primary trigger and scope, then the retrieval fields, then the examples, then the exclusion. The parenthetical example queries are functional for intent matching rather than padding, though the run-on first sentence is dense and could be split for faster scanning.

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?

There is no output schema, and the description compensates by enumerating the returned fields (tithi, nakshatra, Rahu kaal, choghadiya, sunrise/sunset, festivals) plus the default-place behavior and the no-birth-details precondition. For a 2-optional-param read-only tool, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the baseline is 3, and the description earns an extra point by disclosing the defaulting rule for `place` (New Delhi when omitted) and confirming `date` can be any date, not just today. That is real semantic value beyond the schema's format-only 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?

States a specific resource (today's panchang / Hindu calendar for a place) and enumerates exactly what is returned: tithi, nakshatra, yoga, karana, Rahu kaal, Yamaganda, Gulika, Abhijit muhurat, choghadiya, sunrise/sunset, festivals. It also draws an explicit boundary against the birth-chart siblings, so an agent can separate it from vedic_birth_chart without opening a schema.

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?

Gives concrete triggering utterances ("aaj ka panchang", "Rahu kaal today in Pune", "is today Ekadashi"), notes it also works for another date, and states the negative case explicitly: do not use for a person's birth chart or birth star. That is when-to-use, when-not-to-use, and alternative routing all in one place.

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