Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_muhurat_jain_pachakkhan

Read-onlyIdempotent

Retrieve Jain Pachakkhan muhurat timings for a specific date and location, returning the day’s auspicious periods for planning observances.

Instructions

Get the Jain Pachakkhan 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_jain_pachakkhan"
  }
}

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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only that the result includes 'muhurat details' for the day, without noting dependency on location/timezone accuracy or any upstream rejection behavior. An output schema exists, so return shape need not be explained.

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 resource. The second sentence partially restates the first ('auspicious timings' vs 'Pachakkhan timings') but is not enough waste to penalize heavily.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter lookup with a detailed input schema and an output schema, the description is close to sufficient. Its main omission is failing to mention that results depend on accurate lat/lon/tzone and supported language codes.

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?

The description contributes nothing about parameters, but the nested PanchangInput schema documents each field, including the non-ISO language codes (ma/tm/tl) and the literal timezone-offset string format. Since the top-level 'params' wrapper is undocumented, the description's silence leaves a small gap, but the schema does most of the work.

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 the Jain Pachakkhan timings') plus the scoping inputs (date and location). It names a distinct tradition-specific muhurat, so an agent can tell it apart from generic muhurat siblings, though no sibling is named explicitly.

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. The description never distinguishes Jain Pachakkhan from the many other muhurat tools (hora, do_ghati, business_start) or from divine_get_auspicious_timings, leaving the agent to infer selection from the name 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