Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_sankranti_festivals

Read-onlyIdempotent

Get the twelve solar Sankranti transitions for a year, including festival dates, exact transition moments, and punya kala auspicious windows for a specified place and timezone.

Instructions

Get Sankranti festivals for a year.

Returns the twelve solar Sankranti transitions (Makar, Kumbha, Meena, Mesha, and so on) with dates, transition moments, and punya kala (auspicious) windows.

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_sankranti_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.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds the meaningful scope detail that exactly twelve solar transitions are returned with punya kala windows, but that largely restates what the output schema carries, and it says nothing about compute cost, location-dependence, or why five required params are needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two front-loaded sentences: the action and scope first, then a compact enumeration of the returned data. No filler, no repetition, nothing that could be cut without losing information.

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 7 parameters (5 required), a rich output schema, and full annotations, the description is adequate but thin on one point an agent actually needs: that place/lat/lon/tzone drive the computed transition moments and punya kala windows, so omitting them or passing wrong values changes results. Otherwise the required context 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?

Schema coverage is 100% and the schema already explains lan's language codes, include_name's effect, and example values for lat/lon/place/tzone. The description adds no parameter meaning beyond that, so the baseline 3 is appropriate.

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 Sankranti festivals for a year') and scopes the result precisely: twelve solar Sankranti transitions with dates, transition moments, and punya kala windows. It does not, however, distinguish itself from siblings like divine_get_festivals_by_month or divine_get_tamil_festivals, which an agent could plausibly confuse it with.

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

Usage Guidelines2/5

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

The description implies usage by stating 'for a year' but gives no explicit when-to-use, when-not-to-use, or alternative routing (e.g., use festivals_by_month for a broader festival list, or a regional tool for Tamil/Malayalam naming). The agent must infer the boundary from the tool name 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