Skip to main content
Glama

Moon Dasha Vedic Astrology

Panchang

panchang
Read-onlyIdempotent

Calculate the Vedic panchang (Hindu almanac) of a day at a place with Moon Dasha: the weekday; tithi, nakshatra, yoga and karana with their change times; the Moon's sign; the lunar month (Amanta and Purnimanta); sunrise, sunset, moonrise and moonset; Rahu Kaal, Gulikai Kalam, Yamaganda, Dur Muhurtam, Abhijit Muhurat, Vijaya Muhurta, Amrit Kalam and Brahma Muhurta; the 24 horas; planets changing sign or nakshatra that day; and when the next Purnima, Amavasya and Ekadashis run. No Choghadiya or festival dates. Needs the place (a place_id from find_place); the date defaults to today there, and the answer then also says what is running now. The figures are Moon Dasha's calculations. Interpret them with care and never predict death, illness, a child's sex, markets, elections or court cases.

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_id": "<place_id>"
    },
    "name": "panchang"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe day, YYYY-MM-DD. Default today at the place, by its own clock; the answer then also says what is running now.
nodeNoRahu and Ketu by the mean node (default) or the true node.
sunriseNoWhich sunrise opens the day: apparent (the default, as moondasha.com times it: the upper limb with refraction) or classical (the centre of the disc on the true horizon, without refraction).
ayanamsaNoDefault Lahiri. Krishnamurti is the KP ayanamsa.
place_idYesThe place_id find_place returned for the place.

Output Schema

NameRequiredDescriptionDefault
dayYesThe span the limbs, windows and horas cover.
nowYesWhat is running at the moment of the call, when the day is today at the place; null otherwise.
sunYes
dateYes
linkYes
moonYes
yogaYes
horasYes
placeYes
tithiYes
karanaYes
weekdayYes
calendarYes
settingsYes
moon_signYes
nakshatraYes
lunar_monthYes
time_windowsYes
planet_changesYes
next_lunar_datesYesThe next Purnima, Amavasya and both Ekadashis not over at the day's start, as tithi spans; the day a fast is kept follows local rules.
weekday_sanskritYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, and the description adds substantive context beyond that: the figures come from Moon Dasha's calculations, the default-date call additionally reports what is currently running, and the output is framed with an interpretation caveat (never predict death, illness, a child's sex, markets, elections or court cases). That is unusual, decision-relevant disclosure for a read-only tool.

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?

Purpose and scope are front-loaded and every clause carries information, but the middle is one very long semicolon-chained enumeration of output items. It is dense rather than padded; a slight structural trim (splitting the output list) would improve scanability.

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?

Although an output schema exists and return values need not be described, the description still covers what the tool computes, its data source, its required input provenance, its date default behaviour and its interpretation limits. Nothing an agent needs in order to call it correctly is missing for a 5-parameter, closed-world read tool.

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% and the schema already documents date defaulting, node/sunrise/ayanamsa enums and the find_place provenance of place_id, so the description's parameter information is essentially restated. It adds no new syntax, format or constraint beyond the schema — the correct baseline of 3.

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 specific verb and resource ("Calculate the Vedic panchang ... of a day at a place") and then enumerates exactly what is returned — tithi, nakshatra, yoga, karana, muhurtas, horas, sign changes. It actively bounds the scope against neighbours by stating "No Choghadiya or festival dates," so an agent can distinguish it from siblings 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear preconditions — a place_id from find_place, date optional and defaulting to today at that place — plus an explicit exclusion (no Choghadiya, no festival dates). It stops short of naming which sibling to use instead for those excluded outputs, so it is clear context without full alternative routing.

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