Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_chandrabalam_and_tarabalam

Read-onlyIdempotent

Get Chandrabalam (Moon's strength by rashi) and Tarabalam (birth nakshatra auspiciousness) for a date and location to select auspicious muhurta timings.

Instructions

Get Chandrabalam and Tarabalam for a given date and location.

Chandrabalam is Moon's strength for each rashi. Tarabalam is the auspiciousness based on birth nakshatra. Both important for muhurta selection.

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_chandrabalam_and_tarabalam"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

A3.5/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 the safety profile is fully covered. The description adds that the output feeds muhurta selection, which is genuine context, but says nothing about response shape, per-rashi granularity, or whether results are computed for all rashis/nakshatras or only the queried one.

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?

Three short sentences, front-loaded with the action and resource, then two glosses that genuinely help an agent unfamiliar with the terminology. No filler beyond a slightly redundant closing clause.

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?

An output schema exists, so return-value explanation is not required, and the annotations cover the safety profile. What remains missing is minor but real: whether the caller needs birth data for Tarabalam (none is in the schema) and how location precision is handled. For a single-parameter read tool this is close to sufficient.

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?

Reported schema description coverage is 0% at the top level, so the description should carry more weight, yet it only says 'for a given date and location.' That maps loosely onto the date and place/lat/lon fields but adds no format, timezone, or language semantics; notably the description never mentions that Tarabalam depends on a birth nakshatra while the input schema exposes no such parameter, leaving the computation basis unclear. The nested field descriptions in the schema do most of the work here.

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 states a specific verb ('Get') and named resources (Chandrabalam and Tarabalam), and even defines both terms in astrological language, so an agent can tell what data comes back. It does not, however, contrast itself against nearby siblings such as divine_get_auspicious_timings or divine_get_choghadiya, which also serve muhurta selection, so differentiation is left to the agent.

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?

'Both important for muhurta selection' gives an implied use context, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many timing-related siblings. The agent must infer that this is a muhurta sub-lookup rather than the primary timing tool.

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