Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_nivas_and_shool

Read-onlyIdempotent

Get Nivas and Shool for a date and location to identify deity resting places and inauspicious travel directions.

Instructions

Get Nivas and Shool (directional inauspicious timings) for a date and location.

Shool indicates inauspicious directions for travel on specific days. Nivas shows the resting place of certain deities.

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

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, destructiveHint=false and openWorldHint, so safety and repeatability are covered. The description adds domain semantics (what Shool and Nivas mean) but says nothing about computation behavior, latitude/longitude sensitivity, or timezone handling beyond what annotations and schema give.

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?

The primary action is front-loaded in the first sentence, and the two follow-on lines defining Shool and Nivas are short and informative. Slightly more text than strictly needed, but no sentence is wasteful.

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-value explanation is not required, and the single nested params object is documented in the schema. What is missing is disambiguation from sibling timing tools and any hint about date/location/timezone requirements, leaving the definition adequate but not complete for a crowded catalog.

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 only implies the inputs with 'a date and location', adding no meaning for timezone, language, or coordinate formats. The nested PanchangInput schema does carry per-field descriptions and examples, which partially offsets the reported 0% top-level coverage, but the description itself contributes little parameter semantics.

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?

Names a specific verb and resource ('Get Nivas and Shool ... for a date and location') and glosses both terms as directional inauspicious timings, so an agent knows the content. It does not distinguish itself from closely overlapping siblings such as divine_get_inauspicious_timings or divine_get_auspicious_timings, which is the main gap.

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?

Usage is only implied by 'for a date and location' — there is no statement of when to prefer this over the other timing tools, no prerequisites, and no exclusions. With many sibling timing tools in the catalog, the absence of any routing guidance is a real weakness.

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