Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_ritu_and_anaya

Read-onlyIdempotent

Retrieves Ritu (Hindu season) and Anaya details for a given date and location, returning the current season and related calendar information.

Instructions

Get Ritu (season) and Anaya details for a given date and location.

Returns the current Hindu season (Vasant, Grishma, Varsha, Sharad, Hemant, Shishir) and related calendar information.

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": {
      "params": "<params>"
    },
    "name": "divine_get_ritu_and_anaya"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds some value by stating what is returned (the current Hindu season plus related calendar information) and enumerating the season names, but it says nothing about how the season is determined, whether results depend on timezone boundaries, or what 'Anaya' behaviorally entails.

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, and the season enumeration earns its place. The trailing phrase 'and related calendar information' is vague filler that tells the agent nothing concrete.

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 in the description. Still, the undefined term 'Anaya' and the lack of any positioning against sibling calendar tools leave an agent guessing about scope for a nine-field, location-and-timezone-dependent calculation tool.

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?

The description only says inputs are a 'date and location', omitting that latitude, longitude, timezone offset and an optional non-ISO language code are also part of the required params object. The nested PanchangInput schema does describe each field in detail, which keeps this at baseline rather than lower, but the description itself contributes almost no parameter meaning beyond the date/location hint.

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 first sentence gives a specific verb ('Get') and two named resources (Ritu/season and Anaya) scoped to a date and location, and the second sentence enumerates the six possible season values so the agent knows what 'Ritu' means. However, 'Anaya' is never defined at all, and nothing distinguishes this from the many other panchang/calendar siblings, so the purpose is clear but not fully self-contained.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives among the numerous calendar siblings such as divine_get_chandramasa or divine_get_other_calendars_and_epoch. The phrase 'for a given date and location' only implies the input context; it does not tell an agent which tool to pick for a season query versus a broader panchang request.

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