Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_festivals_by_month

Read-onlyIdempotent

Get all Hindu festivals for a specified Hindu calendar month, year, and place, with optional localized names to plan observances accurately.

Instructions

Get all Hindu festivals for a specific Hindu calendar month.

Supports all 12 Hindu months: Margashirsha, Pausha, Magha, Phalguna, Chaitra, Vaishakha, Jyeshtha, Ashadha, Shravana, Bhadrapada, Ashvina, Kartika.

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": {
      "hindu_month": "<hindu_month>",
      "year": "<year>",
      "place": "<place>",
      "lat": "<lat>",
      "lon": "<lon>",
      "tzone": "<tzone>"
    },
    "name": "divine_get_festivals_by_month"
  }
}

Input Schema

NameRequiredDescriptionDefault
lanNoLanguage code for festival names (default 'en'). One of: en (English), hi (Hindi), bn (Bengali), ma (Marathi), tm (Tamil), tl (Telugu), ml (Malayalam), kn (Kannada). Note these are not ISO codes - use 'ma', 'tm', 'tl', not 'mr', 'ta', 'te'.en
latYesLatitude (e.g., '28.6139')
lonYesLongitude (e.g., '77.2090')
yearYesYear (e.g., '2025')
placeYesPlace name (e.g., 'New Delhi')
tzoneYesTimezone offset (e.g., '5.5')
hindu_monthYesHindu month: margashirsha, pausha, magha, phalguna, chaitra, vaishakha, jyeshtha, ashadha, shravana, bhadrapada, ashvina, kartika
include_nameNoAdd a human-readable 'name' to every festival, localised by 'lan' (e.g. 'Anant Chaturdashi', or 'अनंत चतुर्दशी' with lan='hi'). 'YES' (default here) or 'NO'. Without it the response carries only raw keys such as anant_chaturdashi.YES

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

B3.4/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 that the result is the complete set of festivals for the month, but omits that results are location- and timezone-dependent and that naming/localization is controlled by include_name and lan.

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 core purpose front-loaded and no filler. The 12-month enumeration is redundant against the schema's hindu_month description, which slightly dilutes an otherwise efficient definition.

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?

With an output schema, full parameter descriptions and complete annotations, most of the burden is carried structurally. The remaining gap is that nothing explains why six required parameters exist for a month-based query or how location affects the returned festivals.

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 is 100%, so the schema already documents every parameter including the month enum, lan codes and include_name. The description's list of the 12 month names largely restates the hindu_month enum, adding only capitalization, and says nothing about lat/lon/tzone/place 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?

The description states a specific verb and resource ('Get all Hindu festivals') scoped to a Hindu calendar month, which implicitly distinguishes it from the by-date sibling. It stops short of naming divine_get_festivals_by_date or the regional festival siblings, so differentiation is inferred rather than stated.

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 scope phrase 'for a specific Hindu calendar month'; there is no explicit when-to-use or when-not-to-use guidance versus the by-date or regional festival tools. It also never explains that a month query still requires place/lat/lon/tzone, which an agent could easily misread as optional context.

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