Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_sun_moon

Read-onlyIdempotent

Get sunrise, sunset, moonrise, and moonset timings for a specific date and location, plus related astronomical data, to support daily planning or astrology queries.

Instructions

Get sun and moon rise/set timings for a given date and location.

Returns sunrise, sunset, moonrise, moonset times and related astronomical data.

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

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 the safety profile is fully covered elsewhere. The description adds the useful fact that output includes sunrise, sunset, moonrise, moonset and 'related astronomical data', but says nothing about timezone handling, language-dependent output, or upstream validation failures.

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 action and scope. The second sentence largely restates the first (rise/set vs. sunrise/sunset) and adds only 'related astronomical data', so it is efficient but slightly redundant.

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 tool is conceptually simple and has both annotations and an output schema, so much of the burden is offloaded. Still, a required timezone offset and the language-code quirk are exactly the details an agent needs before calling, and the description omits them.

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?

Reported schema description coverage is 0%, so the description carries the burden, yet it only alludes to 'a given date and location'. It does not mention the required timezone offset (tzone), the lat/lon requirement, or the non-ISO language codes, all of which are easy-to-miss inputs for this tool.

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 sun and moon rise/set timings') plus the scoping inputs (date and location), which is far more precise than the name alone. It does not, however, differentiate itself from related timing siblings such as divine_get_auspicious_timings or divine_get_choghadiya, so an agent must infer the boundary from names.

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, no mention of prerequisites, and no named alternative. The phrase 'for a given date and location' describes input scope, not selection guidance, so the agent gets no help choosing this over sibling timing 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