Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_festivals_by_date

Read-onlyIdempotent

Retrieve all Hindu festivals and observances for a specific date and location, with optional localized festival names.

Instructions

Get festivals falling on a specific date.

Returns all Hindu festivals and observances for a given date and location. Each festival carries a human-readable 'name' unless include_name='NO', localised by 'lan'.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real behavioral context by noting the result is scoped by date AND location, that names are localized per 'lan', and that raw keys are returned when include_name='NO'. It does not mention error behavior for unsupported language codes or missing/invalid coordinates.

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?

Three short sentences, front-loaded with the core action and followed by return-shape and name-flag details. No filler; the only mild redundancy is restating 'festivals' three times.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What remains for an agent to call correctly — that results are date- and location-scoped, that names require include_name, and that output is language-sensitive — is present.

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 schema description coverage is 0% (the schema itself does carry per-field text), so the description should compensate; it only explains two of the nine fields, 'lan' localization and the include_name toggle, and says nothing about the day/month/year format, place, lat/lon, or the timezone parameter's expected offset format.

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: retrieve Hindu festivals and observances for a specific date and location. The scope ('all Hindu festivals and observances') is clear. It does not name divine_get_festivals_by_month or the region-specific siblings (Tamil/Malayalam/Sankranti), so differentiation is left to inference from 'specific date'.

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 the phrase 'falling on a specific date' — an agent can infer this is the day-level lookup versus the month-level sibling, but there is no explicit when-to-use or when-not guidance, nor any mention of the region-specific festival tools as alternatives.

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