Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_inauspicious_timings

Read-onlyIdempotent

Retrieve inauspicious time windows—Rahu Kaal, Yamaganda, Gulika Kaal, and Dur Muhurat—for a date and location to help avoid unfavorable activities.

Instructions

Get inauspicious timings for a given date and location.

Returns unfavorable time windows: Rahu Kaal, Yamaganda, Gulika Kaal, Dur Muhurat. Useful for avoiding inauspicious activities.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds only the nature of the returned windows; it discloses nothing about upstream validation, language-dependent output, or failure modes for out-of-range dates/locations. No annotation contradiction.

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 lines, front-loaded with purpose and immediately followed by the concrete outputs. Slightly wasteful in that the return-value enumeration is largely restated by the output schema, but it is not padded or vague.

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?

For a read-only tool with an output schema and full annotations, the description covers the essentials but omits input-format expectations (string-typed day/month/year, tzone as a decimal offset) that an agent must get right. Listing return values while omitting those constraints puts emphasis in the wrong place.

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 at 0% for the single top-level 'params' object, so the description must carry the load, yet it only says 'a given date and location'. It says nothing about the mandatory timezone offset string, latitude/longitude, or the non-ISO language code behavior — the most error-prone aspects of this input.

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 inauspicious timings') and enumerates what comes back (Rahu Kaal, Yamaganda, Gulika Kaal, Dur Muhurat), which is enough to distinguish it from the auspicious-timings sibling. It stops short of naming that sibling, so the differentiation is inferred from the word 'inauspicious' rather than stated.

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?

'Useful for avoiding inauspicious activities' is the only usage cue and it describes the astrological purpose, not the tool-selection condition. There is no explicit guidance on when to prefer this over divine_get_auspicious_timings or divine_get_choghadiya, and no note that it requires a full date plus coordinates.

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