Skip to main content
Glama
Sign In

FestivalFinder

by io.github.everyai-com
OverviewDiscussionsAdmin

Next festival

next_festival
Read-onlyIdempotent

Find the first Hindu festival or sankranti falling on or after a given date (looks into the following year if needed; 2020-2040 only). Use for 'what is the next festival?' questions. Do NOT use for a list; use list_festivals or festivals_in_month.

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": {
      "from_date": "<from_date>"
    },
    "name": "next_festival"
  }
}

Input Schema

NameRequiredDescriptionDefault
from_dateYesStart date YYYY-MM-DD (inclusive), year 2020-2040, e.g. 2026-10-10. Use today's date for 'next'.

Output Schema

NameRequiredDescriptionDefault
dateYesComputed Gregorian date, YYYY-MM-DD (approximate, +/-1 day at tithi edges).
nameYesFestival name, e.g. "Diwali / Lakshmi Puja" or "Makara Sankranti / Pongal".
aboutYesShort meaning and the lunar or solar rule that fixes the date.
monthYesAmanta lunar month name in effect on that date, e.g. Ashwin.
tithiYesLunar 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.

  1. Changed3 schema fields changed
    • changedInput schema / properties / from_date / description
      Previous value: -"Date YYYY-MM-DD to search for the next festival on or after"New value: +"Start date YYYY-MM-DD (inclusive), year 2020-2040, e.g. 2026-10-10. Use today's date for 'next'."
    • addedInput schema / properties / from_date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • 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"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "date": {
-      "description": "The date of the festival.",
-      "format": "date",
-      "type": "string"
-    },
-    "description": {
-      "description": "A brief description of the festival.",
-      "type": "string"
-    },
-    "location": {
-      "description": "The location where the festival is held.",
-      "type": "string"
-    },
-    "name": {
-      "description": "The name of the festival.",
-      "type": "string"
-    }
-  },
-  "required": [
-    "name",
-    "date",
-    "location"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed2 schema fields changed
    • addedInput schema / properties / from_date / description
      Added value: +"Date YYYY-MM-DD to search for the next festival on or after"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "date": {
+      "description": "The date of the festival.",
+      "format": "date",
+      "type": "string"
+    },
+    "description": {
+      "description": "A brief description of the festival.",
+      "type": "string"
+    },
+    "location": {
+      "description": "The location where the festival is held.",
+      "type": "string"
+    },
+    "name": {
+      "description": "The name of the festival.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "date",
+    "location"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds genuine behavioral context beyond them: the lookahead into the following year and the hard 2020-2040 bound. It does not need to describe returns because an output schema exists.

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: purpose first, then usage cue, then exclusions. Every sentence earns its place and the most decision-relevant information is front-loaded.

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 tool with rich annotations and an output schema, the description supplies everything an agent needs: scope, fallback behavior, valid year range, and sibling routing. No material gap remains.

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 single from_date parameter is fully documented (format, pattern, inclusive semantics, example, and the hint to pass today's date). The description adds only the inclusive/lookahead framing, so the baseline 3 for schema-driven parameters 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?

Specific verb (find) plus resource (first Hindu festival or sankranti on or after a date), with scope constraints (following year fallback, 2020-2040 window). It also names the siblings it is not (list_festivals, festivals_in_month), so an agent can disambiguate without opening another 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?

Explicit when-to-use ("what is the next festival?" questions) and explicit when-not-to-use ("Do NOT use for a list"), with the two alternative tools named. Nothing is left to inference.

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

All FestivalFinder toolsInspect
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.

Resources