Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_panchang

Retrieve Vedic panchang details by date, time, latitude, longitude, and timezone for daily astrological planning and timing decisions.

Instructions

Execute panchang AstroChalit API

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": {
      "date": "<date>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_panchang"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format (e.g. 2026-11-04)
timeNoTime in HH:MM:SS format (e.g. 10:30:00)10:30:00
latitudeYesLatitude of the location
timezoneNoTimezone (Default: 'Asia/Kolkata')Asia/Kolkata
longitudeYesLongitude of the location

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing: no indication of whether this is a read operation, what data is returned, whether an external API call or auth is involved ("AstroChalit API" hints at a remote dependency but never explains it), or what happens with defaults.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with nothing superfluous, but the brevity is under-specification rather than economy — "AstroChalit API" is vendor jargon that consumes the whole description without informing the caller.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, three required, no output schema, and no annotations, the description needed to explain what the returned panchang contains and how the location/time drive results. It covers none of this, leaving the agent unable to predict the response shape at all.

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 every parameter including date format, time default, timezone default, and lat/long ranges is already documented in the schema. The description adds no meaning beyond that, but the baseline of 3 applies when the schema does the work.

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

Purpose2/5

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

The description restates the tool name and vendor ("panchang AstroChalit API") without saying what panchang computation produces — no mention of tithi, nakshatra, yoga, or any output element. An agent learns nothing beyond the name itself, and nothing distinguishes it from siblings like get_dashakoot or get_compatibility_check that also consume date/place.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling astrological tools. The agent must guess whether panchang is the right call versus divisional chart or dasha tools.

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