FestivalFinder

Festival details

festival_details

Read-onlyIdempotent

Look up one festival by name in a given year and return its computed date, lunar month, tithi and the rule behind it. Name matching is case-insensitive and partial (e.g. 'diwali', 'holi', 'makara'); first match wins. Use when the user asks when a specific festival is. Do NOT use to list several; use list_festivals.

Input Schema

Name	Required	Description	Default
`name`	Yes	Festival name or part of it, case-insensitive, e.g. "Diwali", "Holi", "Maha Shivaratri", "Onam", "Makara Sankranti".
`year`	Yes	Gregorian year, 2020-2040, e.g. 2026

Output Schema

Name	Required	Description
`date`	Yes	Computed Gregorian date, YYYY-MM-DD (approximate, +/-1 day at tithi edges).
`name`	Yes	Festival name, e.g. "Diwali / Lakshmi Puja" or "Makara Sankranti / Pongal".
`about`	Yes	Short meaning and the lunar or solar rule that fixes the date.
`month`	Yes	Amanta lunar month name in effect on that date, e.g. Ashwin.
`tithi`	Yes	Lunar day index at IST noon on that date, 0-29 (0 = Shukla Pratipada, 29 = Amavasya), as 'index N'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 15, 2026

changedInput schema / properties / name / description

Previous value: -"The name for this request."New value: +"Festival name or part of it, case-insensitive, e.g. \"Diwali\", \"Holi\", \"Maha Shivaratri\", \"Onam\", \"Makara Sankranti\"."

addedInput schema / properties / name / minLength
```
Added value: +1
```

changedInput schema / properties / year / description

Previous value: -"The year as a number."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": {
+    "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"
+}

Changed1 schema field changedOct 10, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "date": {
-      "description": "The specific date when the festival occurs.",
-      "format": "date",
-      "type": "string"
-    },
-    "duration": {
-      "description": "The duration of the festival (e.g., one day, multiple days).",
-      "type": "string"
-    },
-    "location": {
-      "description": "The primary location where the festival is celebrated.",
-      "type": "string"
-    },
-    "name": {
-      "description": "The name of the festival.",
-      "type": "string"
-    },
-    "ruleExplanation": {
-      "description": "The explanation of the rule determining the festival's date.",
-      "type": "string"
-    },
-    "significance": {
-      "description": "The cultural or religious significance of the festival.",
-      "type": "string"
-    },
-    "traditions": {
-      "description": "A list of traditional activities or customs associated with the festival.",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "year": {
-      "description": "The year in which the festival occurs.",
-      "type": "number"
-    }
-  },
-  "required": [
-    "name",
-    "year",
-    "date",
-    "ruleExplanation"
-  ],
-  "type": "object"
-}New value: +null

Changed3 schema fields changedOct 6, 2026

addedInput schema / properties / name / description
```
Added value: +"The name for this request."
```
addedInput schema / properties / year / description
```
Added value: +"The year as a number."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "date": {
+      "description": "The specific date when the festival occurs.",
+      "format": "date",
+      "type": "string"
+    },
+    "duration": {
+      "description": "The duration of the festival (e.g., one day, multiple days).",
+      "type": "string"
+    },
+    "location": {
+      "description": "The primary location where the festival is celebrated.",
+      "type": "string"
+    },
+    "name": {
+      "description": "The name of the festival.",
+      "type": "string"
+    },
+    "ruleExplanation": {
+      "description": "The explanation of the rule determining the festival's date.",
+      "type": "string"
+    },
+    "significance": {
+      "description": "The cultural or religious significance of the festival.",
+      "type": "string"
+    },
+    "traditions": {
+      "description": "A list of traditional activities or customs associated with the festival.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "year": {
+      "description": "The year in which the festival occurs.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "name",
+    "year",
+    "date",
+    "ruleExplanation"
+  ],
+  "type": "object"
+}

First observedOct 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needed to add matching behavior — and it does, disclosing case-insensitive partial matching and 'first match wins', which an agent could not infer from the schema. It stops short of saying what happens when nothing matches (empty result vs. error), which is the one behavior still left to guess.

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 sentences, zero filler: purpose and return payload first, matching semantics second, routing guidance last. Everything is front-loaded and each sentence earns its place.

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?

With an output schema present, the return shape need not be explained, and the description correctly focuses on matching behavior and sibling routing. The only omission is the no-match outcome, which matters for a tool advertising 'first match wins' where zero matches is a plausible input case.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so 'name' and 'year' are already documented with examples and the 2020-2040 bound, making the baseline 3. The description still adds real meaning beyond the schema by stating the tie-break rule ('first match wins') for an ambiguous partial name, which is a disambiguation policy the schema cannot express.

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 and resource ('look up one festival by name in a given year') and goes on to name the exact payload returned (computed date, lunar month, tithi, governing rule). The singular 'one festival' plus the explicit hand-off to list_festivals makes it unmistakable against its siblings.

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 an explicit positive trigger ('Use when the user asks when a specific festival is') and an explicit exclusion with the named alternative ('Do NOT use to list several; use list_festivals'). This is the full when/when-not/alternative pattern.

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.

Festival details

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources