Asterwise

Panchanga Calendar

asterwise_get_panchanga_calendar

Read-onlyIdempotent

Panchanga for every day of a month at a location, one entry per day. Each day has its sunrise tithi, vara, nakshatra, yoga, karana and Rahu Kaal, plus sunrise, sunset, moonrise, moonset, paksha, lunar month (amanta and purnimanta, with Adhik months), Bhadra windows, and every tithi, nakshatra, yoga and karana active that day with ISO start and end times.

WORKFLOW: BEFORE: asterwise_geocode — when you only have a place name. AFTER: asterwise_get_panchanga — full timings for one chosen day.

INPUT CONTRACT: calendar.year 1900-2100, calendar.month 1-12, calendar.lat, calendar.lon, calendar.timezone (IANA; default Asia/Kolkata — set it for places outside India).

DO NOT CONFUSE WITH: asterwise_get_panchanga — one day with all timings. asterwise_get_festival_calendar — festivals and vrats rather than daily limbs.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-panchanga-calendar/

Input Schema

Name	Required	Description	Default
`calendar`	Yes	Monthly Panchanga calendar parameters.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 28, 2026

addedInput schema / properties / calendar / properties / ayanamsa

Added value: +{
+  "default": "lahiri",
+  "description": "Ayanamsa for nakshatra and yoga.",
+  "enum": [
+    "lahiri",
+    "kp",
+    "raman",
+    "tropical"
+  ],
+  "type": "string"
+}

addedInput schema / properties / calendar / properties / lat / description
```
Added value: +"Latitude in decimal degrees, north positive."
```
addedInput schema / properties / calendar / properties / lon / description
```
Added value: +"Longitude in decimal degrees, east positive."
```
addedInput schema / properties / calendar / properties / month / description
```
Added value: +"Month number 1-12."
```

addedInput schema / properties / calendar / properties / timezone

Added value: +{
+  "default": "Asia/Kolkata",
+  "description": "IANA timezone of the location, e.g. 'America/New_York'. Default: Asia/Kolkata.",
+  "type": "string"
+}

addedInput schema / properties / calendar / properties / year / description
```
Added value: +"Calendar year, 1900-2100."
```

First observedApr 22, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: per-day entry semantics, Adhik month handling, Bhadra windows, and ISO start/end times for active limbs. It stops short of stating rate limits or auth requirements, so it is strong but not exhaustive.

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?

Front-loaded with the capability, then cleanly partitioned into WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH, and a docs pointer. The dense enumeration of returned fields is information the agent needs for a monthly calendar tool, not padding.

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?

With an output schema present, return values need not be detailed, yet the description still summarizes them. Workflow ordering, parameter pitfalls, sibling disambiguation, and an error/output contract link are all supplied, so nothing needed to call this correctly is missing.

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?

Schema description coverage is 100%, so the baseline is 3. The INPUT CONTRACT largely restates schema ranges, but the timezone note (IANA, default Asia/Kolkata, must be set for places outside India) flags the single most likely misconfiguration and adds practical meaning the schema default alone does not convey.

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 opening sentence states a specific verb (get Panchanga), resource (calendar), and scope (every day of a month at a location, one entry per day), then enumerates the returned limbs. It explicitly names the siblings it is not (asterwise_get_panchanga, asterwise_get_festival_calendar), so an agent can route 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?

A labeled WORKFLOW block gives an explicit BEFORE (geocode when only a place name is known) and AFTER (get_panchanga for one chosen day) chain, and the DO NOT CONFUSE WITH block names the two nearest alternatives with the condition that selects each.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Asterwise tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?