Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_muhurat_hora

Read-onlyIdempotent

Retrieve Hora (planetary hour) timings and auspicious muhurat details for a given date and location.

Instructions

Get the Hora (planetary hour) timings for a given date and location.

Returns auspicious timings for the day with muhurat details.

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

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, destructiveHint=false and openWorldHint, so the safety profile is fully covered without description help. The description adds only a light statement about the return ('auspicious timings for the day with muhurat details'), and says nothing about astronomy-dependent behavior such as whether Hora spans day and night, whether location accuracy matters, or what happens for unsupported dates.

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 verb and resource, with no padding or marketing language. The second sentence is slightly redundant and vague ('muhurat details') but does not obstruct comprehension.

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 described, and annotations cover the read-only profile. However, for a tool whose value depends on being chosen over several similar timing tools, the absence of any selection guidance or parameter prerequisites leaves it only minimally complete.

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 contributes zero parameter meaning; it only restates 'date and location'. The reported top-level schema coverage is 0% (the single nested 'params' object carries no description of its own), so the description was the place to flag required inputs like lat/lon/tzone and the non-ISO language codes ('ma', 'tm', 'tl') that the schema warns about — none of that is surfaced 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?

Uses a specific verb ('Get') with a specific resource ('Hora (planetary hour) timings') and expands the term for agents unfamiliar with Vedic terminology, scoping it to a date and location. It does not, however, distinguish itself from adjacent timing tools such as divine_get_choghadiya, divine_get_gowri_panchangam, or divine_get_auspicious_timings, so an agent must guess which one to pick.

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?

No when-to-use guidance is given, and no alternatives are named despite a dense sibling set of muhurat_* and panchang-style timing tools. The only usage signal is the implicit 'given a date and location', which is not a selection criterion.

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