Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_panchang

Read-onlyIdempotent

Retrieve complete daily Panchang data for a specific date and location, including tithi, nakshatra, yoga, karana, sunrise/sunset, and rahu kaal.

Instructions

Get the complete daily Panchang for a given date and location.

Returns comprehensive Vedic calendar data including tithi, nakshatra, yoga, karana, sunrise/sunset, moonrise/moonset, rahu kaal, and more.

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": {
      "params": "<params>"
    },
    "name": "divine_get_panchang"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only the payload contents, saying nothing about upstream rejection behavior, timezone/language requirements, or rate limits. What it contributes is modest but consistent with the annotations.

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?

Two short sentences, front-loaded with the core purpose and followed by the return contents. No filler, though the return enumeration partly duplicates what the output schema already provides.

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

Completeness3/5

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

The output schema covers return values and annotations cover safety, so the description needn't re-explain those. Still, for a tool whose parameters carry several non-obvious format conventions and which sits among many panchang siblings, the definition leaves the agent without selection or input-format guidance.

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

Parameters2/5

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

The description mentions only 'date and location', while the input actually requires day, month, year, place, lat, lon, and tzone, plus an optional 'lan' with non-ISO language codes. With schema description coverage reported at 0%, the description needs to compensate for the quirks (string-typed numerics, timezone as a decimal offset, non-standard language codes) and does not.

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 and resource — 'Get the complete daily Panchang for a given date and location' — and enumerates the returned elements (tithi, nakshatra, yoga, karana, sunrise/sunset, rahu kaal). However, it never distinguishes itself from overlapping siblings such as divine_get_gowri_panchangam, divine_get_choghadiya, or divine_get_auspicious_timings, which an agent could easily confuse with a 'complete Panchang' call.

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

Usage Guidelines2/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 when-not-to-use condition, and no named alternative. The agent is told what the tool fetches but not why it should prefer it over the several panchang-adjacent siblings.

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