Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_malayalam_festivals

Read-onlyIdempotent

Retrieve major Kerala festivals such as Vishu, Onam, and Thrissur Pooram for a given year and location, including dates and images for Malayalam festival planning.

Instructions

Get major Malayalam (Kerala) festivals for a year.

Returns Vishu Kani, Onam, Thrissur Pooram, Guruvayur Ekadashi, Makara Vilakku and other Kerala 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_malayalam_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

A3.6/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. The description adds that results include dates and images and names specific festivals, but with an output schema present it does not need to describe return values, and it says nothing about ordering, completeness, or whether 'major' filters output.

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; the core purpose is front-loaded and the second sentence usefully enumerates the return content. No filler or redundant restatement of the name.

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 rich annotations, a complete input schema, and an existing output schema, the description covers what is needed to select and call the tool. A note on whether 'major' limits results or on festival count would make it fully complete, but nothing essential is missing.

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 all seven parameters — including lat/lon, place, tzone, and the non-standard language code semantics — are already documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 Malayalam (Kerala) festivals for a year') and enumerates representative festivals (Vishu Kani, Onam, Thrissur Pooram), which lets an agent distinguish it from regional siblings like divine_get_tamil_festivals or divine_get_english_calendar_festivals. The qualifier 'major' leaves some uncertainty about coverage scope, but the intent is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly frames the use case: retrieve Kerala-region festivals for a given year, contrasted implicitly with the other region-specific festival siblings. It does not explicitly state when to prefer divine_get_festivals_by_date or by_month, so a small routing gap remains, but the context is unambiguous.

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