FestivalFinder

List festivals

list_festivals

Read-onlyIdempotent

Compute all major Hindu festivals (Ugadi, Holi, Diwali, Navratri, Ganesh Chaturthi, etc.) and the 12 solar sankrantis for one year, 2020-2040, sorted by date. Dates are approximate (+/-1 day). Use for a full-year overview. Do NOT use for one month (use festivals_in_month) or the next upcoming one (use next_festival).

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>"
    },
    "name": "list_festivals"
  }
}

Input Schema

Name	Required	Description	Default
`year`	Yes	Gregorian year, 2020-2040, e.g. 2026

Output Schema

Name	Required	Description	Default
`year`	Yes	The year that was computed.
`festivals`	Yes	Festivals and sankrantis in that year, sorted by date.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 15, 2026

changedInput schema / properties / year / description

Previous value: -"The year for which to retrieve the festivals, as a 4-digit number, e.g. 2024"New value: +"Gregorian year, 2020-2040, e.g. 2026"

addedInput schema / properties / year / maximum
```
Added value: +2040
```
addedInput schema / properties / year / minimum
```
Added value: +2020
```

changedInput schema / properties / year / type

Previous value: -"number"New value: +"integer"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "festivals": {
+      "description": "Festivals and sankrantis in that year, sorted by date.",
+      "items": {
+        "properties": {
+          "about": {
+            "description": "Short meaning and the lunar or solar rule that fixes the date.",
+            "type": "string"
+          },
+          "date": {
+            "description": "Computed Gregorian date, YYYY-MM-DD (approximate, +/-1 day at tithi edges).",
+            "type": "string"
+          },
+          "month": {
+            "description": "Amanta lunar month name in effect on that date, e.g. Ashwin.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Festival name, e.g. \"Diwali / Lakshmi Puja\" or \"Makara Sankranti / Pongal\".",
+            "type": "string"
+          },
+          "tithi": {
+            "description": "Lunar day index at IST noon on that date, 0-29 (0 = Shukla Pratipada, 29 = Amavasya), as 'index N'.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "date",
+          "about",
+          "tithi",
+          "month"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "year": {
+      "description": "The year that was computed.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "year",
+    "festivals"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 10, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "results": {
-      "description": "List of list festivals entries.",
-      "items": {
-        "properties": {
-          "date": {
-            "description": "The approximate date of the festival or sankranti in YYYY-MM-DD format.",
-            "format": "date",
-            "type": "string"
-          },
-          "name": {
-            "description": "The name of the festival or sankranti.",
-            "type": "string"
-          },
-          "rule": {
-            "description": "The rule or calculation method used to determine the date of the festival or sankranti.",
-            "type": "string"
-          }
-        },
-        "required": [
-          "name",
-          "date",
-          "rule"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "results"
-  ],
-  "type": "object"
-}New value: +null

Changed2 schema fields changedOct 6, 2026

addedInput schema / properties / year / description

Added value: +"The year for which to retrieve the festivals, as a 4-digit number, e.g. 2024"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "description": "List of list festivals entries.",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "The approximate date of the festival or sankranti in YYYY-MM-DD format.",
+            "format": "date",
+            "type": "string"
+          },
+          "name": {
+            "description": "The name of the festival or sankranti.",
+            "type": "string"
+          },
+          "rule": {
+            "description": "The rule or calculation method used to determine the date of the festival or sankranti.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "date",
+          "rule"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

First observedOct 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered structurally. The description adds useful behavioral context beyond that: the precise date-accuracy caveat (+/-1 day), the covered year window, and the fact that output is date-sorted. It does not discuss output size or pagination, but with an output schema present that is largely covered elsewhere.

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?

Three tight sentences, zero filler. The scope statement comes first, the accuracy caveat second, and the routing exclusions last, which is the right front-loading order for an agent deciding whether to call it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only listing tool with an output schema present, the description covers everything actionable: what is returned, the valid year window, the accuracy tolerance, the sort order, and the sibling alternatives. Nothing an agent needs to call it correctly 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?

Only one parameter and schema description coverage is 100%, so the schema already documents the year field with its bounds and an example. The description restates the 2020-2040 range, which is mildly reinforcing but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (compute/list) and resource (Hindu festivals plus solar sankrantis), names concrete examples, and specifies the scope (one year, 2020-2040, sorted by date). It also explicitly distinguishes itself from festivals_in_month and next_festival, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Gives positive guidance ("Use for a full-year overview") and explicit exclusions with named alternatives: not for one month (festivals_in_month) and not for the next upcoming one (next_festival). When/when-not/alternatives are all present and unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FestivalFinder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

List festivals

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources