Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_tamil_festivals

Read-onlyIdempotent

Retrieve major Tamil festival dates and images for a specified year, place, latitude, longitude, and timezone, including Thai Pongal, Puthandu, and Karthigai Deepam.

Instructions

Get major Tamil festivals for a year.

Returns Thai Pongal, Puthandu (Tamil New Year), Karthigai Deepam, Vaikuntha Ekadashi, Arudra Darshan and other Tamil festivals with dates and images.

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": {
      "year": "<year>",
      "place": "<place>",
      "lat": "<lat>",
      "lon": "<lon>",
      "tzone": "<tzone>"
    },
    "name": "divine_get_tamil_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., '2027')
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds that results come back 'with dates and images', which is useful return-shape context, but says nothing about why latitude/longitude/timezone are mandatory or how location affects the festival set.

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 resource, then the return contents. The festival enumeration is slightly redundant with the 'other Tamil festivals' phrase but still useful for recognition.

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 values need no explanation, and the safety profile is covered by annotations. However, for a tool with five required parameters including coordinates and timezone, the description never explains why those inputs are needed, leaving a real gap for an agent assembling the call.

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%, including detailed notes on the non-ISO language codes and the include_name toggle, so the schema carries parameter meaning. The description only echoes the 'year' parameter implicitly and adds no semantics for lat/lon/tzone beyond what the schema states.

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 major Tamil festivals') scoped to a year, and enumerates representative outputs (Thai Pongal, Puthandu, Karthigai Deepam, etc.). The regional qualifier 'Tamil' implicitly carves it out from siblings like divine_get_malayalam_festivals, but no sibling is explicitly named.

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?

The year/Tamil scope implies when the tool is appropriate, but there is no explicit when-to-use, when-not, or pointer to the alternative regional/date-based festival tools. An agent must infer that other calendars exist and require different tools from the sibling names alone.

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