Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_auspicious_timings

Read-onlyIdempotent

Find auspicious time windows (shubh muhurat) for a given date and location to plan weddings, house-warming, travel, and other important activities.

Instructions

Get auspicious timings (shubh muhurat) for a given date and location.

Returns favorable time windows for important activities like weddings, house-warming, travel, etc. (Abhijit Muhurat, Amrit Kaal, etc.).

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so safety is covered. The description adds that the response is a set of favorable time windows categorized by muhurat type, which is useful beyond annotations but stops short of scope or coverage details (e.g., whether the whole day is returned).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core action and followed by the return content and naming examples. No filler or repetition of the tool name.

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 structure need not be explained, and annotations cover safety. However, for a location-and-date-sensitive tool it omits any note on timezone/coordinate requirements and sibling routing, leaving moderate gaps for correct invocation choice.

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?

Top-level schema coverage is reported as 0%, but the nested PanchangInput definition carries per-field descriptions for day, month, year, place, lat, lon, tzone and lan. The description only restates the date-and-location requirement and adds nothing about timezone, coordinate handling, or the non-ISO language codes.

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 auspicious timings (shubh muhurat)') and scopes it to a date and location, plus names the domain concepts (Abhijit Muhurat, Amrit Kaal). It does not distinguish itself from adjacent timing siblings such as divine_get_inauspicious_timings or divine_get_choghadiya, which also return time windows.

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?

The description gives use-case flavor ('weddings, house-warming, travel') but never states when to choose this tool over the inauspicious-timings or choghadiya siblings, nor any prerequisites or exclusions. An agent must infer routing from tool names alone.

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