Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_muhurat_do_ghati

Read-onlyIdempotent

Retrieve the Do Ghati Muhurat for a specific date and location to identify auspicious timings and muhurat details for the day.

Instructions

Get the Do Ghati Muhurat 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_do_ghati"
  }
}

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, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only that the result contains 'auspicious timings for the day with muhurat details', which is modest added value; it says nothing about failure modes for invalid places/coordinates or about the upstream language-code restrictions.

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 operation and its scope, with no filler. The second sentence is mildly redundant with the first ('muhurat details' restates the tool's subject) but costs little.

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 the return values need not be explained, and the read-only annotations carry the safety burden. However, for a domain-specific astrology tool with a jargon term as its core resource and numerous muhurat siblings, the description leaves the agent without enough to decide when this tool is the right one.

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 reported schema description coverage is 0%, and the description contributes only 'date and location', leaving the required nested 'params' object, the string-typed latitude/longitude, and the non-ISO 'lan' codes unaddressed. An agent must open the schema to learn the shape of the call, so the description does not compensate for the coverage gap.

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 uses a specific verb ('Get') and a named resource ('Do Ghati Muhurat'), and scopes it to 'a given date and location', which separates it from unrelated siblings such as divine_get_ascendant_report. It distinguishes itself from the other muhurat siblings only by naming its own muhurat type, without explaining what 'Do Ghati' means or how it differs from divine_get_muhurat_hora or divine_get_auspicious_timings.

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 guidance, no prerequisites, and no named alternative among the many muhurat siblings. 'For a given date and location' hints at the input context but does not tell an agent which muhurat tool to pick for a given question.

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