Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_english_calendar_festivals

Read-onlyIdempotent

Retrieve Hindu festival dates for a specific English calendar month and year by location, with optional localized festival names for planning or reference.

Instructions

Get all Hindu festivals for a specific English calendar month.

Returns festivals falling within a given month of the Gregorian calendar.

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

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')
monthYesEnglish month number ('01' for Jan to '12' for Dec)
placeYesPlace name (e.g., 'New Delhi')
tzoneYesTimezone offset (e.g., '5.5')
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

A3.5/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 the safety profile is covered. The description adds nothing beyond restating the scope; notably it does not disclose that results are location- and timezone-sensitive despite place/lat/lon/tzone being required, though an output schema does cover return shape.

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?

Front-loaded and short, with the core scope in the first sentence. The second sentence largely restates the first, adding only the word Gregorian, so it is mildly redundant rather than wasteful.

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?

Given an output schema, four annotations, and fully documented parameters, the description needs only to convey scope and selection criteria — which it does. The residual gap is the missing differentiation from divine_get_festivals_by_month and the unmentioned location/timezone dependence of results.

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% and includes careful detail (non-ISO language codes, month format '01'-'12', include_name behavior), so the baseline is 3. The description adds no parameter meaning beyond reiterating that the month is Gregorian.

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?

Specific verb and resource: 'Get all Hindu festivals' scoped to 'a specific English calendar month', with a second sentence clarifying Gregorian months. It does not, however, contrast itself with the very similar sibling divine_get_festivals_by_month, so an agent must infer that the distinction is Gregorian-month vs. Hindu-month input.

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 'English calendar month' — an agent can infer this is the Gregorian-month lookup, but there is no explicit when-to-use statement and no mention of the alternative tool for Hindu-month or date-range queries.

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