Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_yoga_panchang

Read-onlyIdempotent

Retrieve the Nitya Yoga for a date and location to identify auspicious or inauspicious qualities of the day based on the Sun-Moon angular relationship.

Instructions

Get yoga (Sun-Moon angular relationship) for a given date and location.

Returns the current yoga from the 27 Nitya Yogas, each indicating auspicious or inauspicious qualities for the day.

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_yoga_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=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and repeatability are covered. The description adds that the result is one of 27 Nitya Yogas with auspicious/inauspicious quality labels, which is useful domain context, but says nothing about lookup determinism, upstream failure modes (e.g., invalid timezone), or localization effects on output.

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, front-loaded sentences with no filler; the definition of yoga comes immediately after the verb. Slightly verbose in restating 'yoga' twice, but nothing needs trimming.

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?

An output schema exists, so return values need not be explained, and the domain concept of Nitya Yogas is covered. However, for a tool requiring a nested PanchangInput with place/lat/lon/tzone, the description omits any hint about required location parameters, leaving a notable gap.

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?

Schema description coverage is reported as 0%, so the schema is not compensating, and the description reduces the inputs to 'a given date and location'. It never mentions the required timezone offset, the language code, or string-format constraints for day/month/year that the schema enforces.

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?

The description gives a specific verb and resource ('Get yoga') and defines it technically as the Sun-Moon angular relationship, plus names the domain (27 Nitya Yogas). It does not distinguish this from the broader sibling divine_get_panchang or from divine_get_nav_pancham_yoga, so an agent cannot tell from the text alone when this narrower call is the right one.

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 or when-not-to-use guidance. Given siblings like divine_get_panchang (which presumably includes yoga among other elements) and divine_get_nav_pancham_yoga, the description never says whether to call this for a single yoga value instead of the full panchang.

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