Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_panchak_rahita

Read-onlyIdempotent

Check whether a date and location fall within the Panchak period, a five-nakshatra span considered inauspicious for activities such as construction and travel.

Instructions

Check Panchak status for a given date and location.

Panchak is a 5-nakshatra period (Dhanishta to Revati) considered inauspicious for certain activities like construction and travel.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine domain context about what Panchak means and why it matters (construction, travel), but says nothing about what the status result looks like or how the period boundaries are resolved — the output schema carries that burden.

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 with the operational statement front-loaded and a compact definition following. Zero filler, though the line break mid-sentence is cosmetic rather than structural.

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

Completeness5/5

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

For a single-input lookup with a full output schema and annotations covering safety and idempotency, the description supplies exactly the missing piece — what Panchak is and why an agent should care. Nothing needed to invoke it correctly is absent.

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?

Schema description coverage registers as 0% at the top level, but the nested PanchangInput definition actually documents each field (day, month, year, place, lat, lon, tzone, lan). The description contributes only 'date and location', omitting timezone and language considerations, so it adds minimal meaning beyond the schema itself.

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 names a specific verb and resource ('Check Panchak status') and even defines the domain concept (a 5-nakshatra period from Dhanishta to Revati). It is clear what the tool returns conceptually, though it does not distinguish itself from nearby siblings such as divine_get_inauspicious_timings 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'for a given date and location' signals the calling context but never states when to prefer this over the auspicious/inauspicious-timings siblings, nor any exclusions or prerequisites. An agent must infer the selection criteria 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