Skip to main content
Glama
adityarya24

Astro Skill MCP Server

by adityarya24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Calculate Panchang

calculate_panchang
Read-onlyIdempotent

Compute the daily Panchang for a place and date: vara, tithi, nakshatra, yoga, karana, and sunrise/sunset times. Returns panchang JSON accepted by the report tools.

Instructions

Compute the daily Panchang for a place and date: vara, tithi, nakshatra, yoga, karana, and sunrise/sunset times. Returns panchang JSON accepted by the report tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude in decimal degrees.
lonYesLongitude in decimal degrees.
dateYesYYYY-MM-DD date for the Panchang.
placeYesPlace name; a label for output, not geocoded.
ayanamsaNoSidereal ayanamsa to calculate with. Default is Lahiri (Chitrapaksha).lahiri
timezone_nameYesIANA timezone of the place, e.g. Asia/Kolkata.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1
  2. Removedv1.1.0
  3. Changed7 schema fields changedv1.0.1
    • addedInput schema / properties / ayanamsa / description
      Added value: +"Sidereal ayanamsa to calculate with. Default is Lahiri (Chitrapaksha)."
    • addedInput schema / properties / ayanamsa / enum
      Added value: +[
+  "lahiri",
+  "chitrapaksha",
+  "raman",
+  "krishnamurti",
+  "kp",
+  "fagan_bradley",
+  "true_chitra",
+  "yukteshwar"
+]
    • changedInput schema / properties / date / description
      Previous value: -"YYYY-MM-DD"New value: +"YYYY-MM-DD date for the Panchang."
    • addedInput schema / properties / lat / description
      Added value: +"Latitude in decimal degrees."
    • addedInput schema / properties / lon / description
      Added value: +"Longitude in decimal degrees."
    • addedInput schema / properties / place / description
      Added value: +"Place name; a label for output, not geocoded."
    • addedInput schema / properties / timezone_name / description
      Added value: +"IANA timezone of the place, e.g. Asia/Kolkata."
  4. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds useful interop context (the JSON feeds the report tools) but says nothing about computation cost, ephemeris data requirements, or how partial/invalid dates are handled.

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?

Two tight sentences: the computation scope and its outputs come first, the downstream integration second. Nothing is padded or redundant.

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?

No output schema exists, but the description compensates by listing the returned Panchang components, so an agent knows what comes back. It does not describe the JSON's shape or nesting, which is the only remaining gap for a six-parameter computation 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%, so lat/lon/date/place/timezone_name/ayanamsa are all documented at the schema level. The description adds no parameter-level detail (e.g. how place relates to geocoding) beyond what the schema already states, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Compute') and a specific resource ('daily Panchang'), and enumerates the outputs (vara, tithi, nakshatra, yoga, karana, sunrise/sunset), which effectively separates it from calculate_kundali, calculate_dasha, and calculate_gochar. It stops short of explicitly naming which sibling to pick instead, so it is clear but not fully differentiated.

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?

Gives an implied usage signal by noting the result is 'accepted by the report tools', routing the agent toward the report pipeline, and the scope is limited to a place and date. There is no explicit when-to-use versus calculate_kundali or when-not guidance.

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

Deploy Server

Other Tools