Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_gowri_panchangam

Read-onlyIdempotent

Retrieve Gowri Panchangam auspicious and inauspicious time segments plus Nalla Neram periods for a date and location.

Instructions

Get the Gowri Panchangam for a given date and location.

Returns auspicious and inauspicious time segments for the day and night (Laabam, Uthi, etc.) plus Nalla Neram (good time) periods, per the South Indian Gowri Panchangam system.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description usefully adds the return content (segment categories plus Nalla Neram), but says nothing about the upstream service dependency implied by openWorldHint, nor about failure modes for invalid coordinates or unsupported language codes.

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 followed by the return contents. The parenthetical '(Laabam, Uthi, etc.)' and the closing 'per the South Indian Gowri Panchangam system' partly restate the tool name, a minor redundancy.

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?

An output schema exists, so return values need no prose, and the nested input schema carries the parameter detail. Given a single nested argument and a read-only profile already pinned by annotations, the definition supplies enough for correct invocation.

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 reported top-level coverage is 0% because the single argument is a nested PanchangInput wrapper, yet that nested schema documents every field (day, month, year, place, lat, lon, tzone, lan) in detail. The description adds only 'date and location', so it neither compensates nor is needed; a 3 baseline is appropriate.

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 Gowri Panchangam') and enumerates what comes back: day/night auspicious and inauspicious segments (Laabam, Uthi) plus Nalla Neram periods. It does not, however, distinguish itself from conceptually similar siblings such as divine_get_choghadiya or divine_get_auspicious_timings, so an agent must infer the difference.

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 by 'for a given date and location' and by naming the South Indian Gowri system, which mildly separates it from North Indian Choghadiya. There is no explicit statement of when to pick this over the Choghadiya or auspicious-timings tools, and no prerequisites are given.

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