Skip to main content
Glama

FestivalFinder

by io.github.everyai-com
OverviewDiscussionsAdmin

Server Details

Computed Hindu festival dates: Diwali, Holi, Navratri, more.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
99.8% over 23 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
everyai-com/sahadeva
GitHub Stars
0
Server Listing
Sahadeva

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct scope: single festival lookup, month listing, year listing, and next-upcoming search. The descriptions even explicitly cross-reference each other with 'Do NOT use X; use Y' guidance, eliminating misselection risk.

Naming Consistency3/5

The names mix conventions: festival_details and festivals_in_month are noun-based, list_festivals is verb_noun, and next_festival is adjective_noun, with inconsistent singular/plural (festival vs festivals). Still readable, but no predictable pattern ties them together.

Tool Count5/5

Four tools is well-scoped for a focused festival-date lookup service, and each maps to a distinct query pattern (one, month, year, next). No tool feels redundant or missing.

Completeness4/5

The surface covers the main read-only query patterns (single, month, year, next) across 2020-2040. Minor gaps like searching all festivals matching a name across years or retrieving additional ritual details are workaroundable but not present.

Available Tools

4 tools
festival_detailsFestival detailsA
Read-onlyIdempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesFestival name or part of it, case-insensitive, e.g. "Diwali", "Holi", "Maha Shivaratri", "Onam", "Makara Sankranti".
yearYesGregorian year, 2020-2040, e.g. 2026

Output Schema

ParametersJSON Schema
NameRequiredDescription
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'.

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.

festivals_in_monthFestivals in monthA
Read-onlyIdempotent
Inspect

List the Hindu festivals and sankrantis that fall in one calendar month of a year (2020-2040), sorted by date; may be empty. Use for questions like 'festivals in October 2026'. Do NOT use for the whole year (use list_festivals) or the next one (use next_festival).

ParametersJSON Schema
NameRequiredDescriptionDefault
yearYesGregorian year, 2020-2040, e.g. 2026
monthYesCalendar month 1-12 (1 = January, 12 = December)

Output Schema

ParametersJSON Schema
NameRequiredDescription
yearYesThe year that was searched.
monthYesThe calendar month that was searched, 1-12.
festivalsYesFestivals in that month, sorted by date (may be empty).

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, and closed-world behavior. The description adds useful behavioral context beyond that: results are sorted by date and may be empty, which helps set expectations for a query tool. It stops short of richer detail such as pagination or result size, but the output schema covers return shape.

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 tightly written sentences with zero waste. The core purpose and scope are front-loaded, and the exclusion guidance follows naturally.

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 simple two-parameter list tool, the description covers purpose, range, ordering, empty-result behavior, and sibling routing. With annotations covering safety and an output schema covering return values, nothing an agent needs in order to call this 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?

Schema description coverage is 100%, so the schema already documents both parameters, including the 2020-2040 year range and 1-12 month mapping. The description restates the year range but adds no syntax or format meaning beyond the schema, so the baseline 3 applies.

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 (List), resource (Hindu festivals and sankrantis), scope (one calendar month of a year, 2020-2040), and ordering (sorted by date). It explicitly differentiates itself from list_festivals and next_festival by naming when not to use it.

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 use case ('festivals in October 2026'), names the alternative tools for whole-year and next-festival queries, and rules out those cases. 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.

list_festivalsList festivalsA
Read-onlyIdempotent
Inspect

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).

ParametersJSON Schema
NameRequiredDescriptionDefault
yearYesGregorian year, 2020-2040, e.g. 2026

Output Schema

ParametersJSON Schema
NameRequiredDescription
yearYesThe year that was computed.
festivalsYesFestivals and sankrantis in that year, sorted by date.

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.

next_festivalNext festivalA
Read-onlyIdempotent
Inspect

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.

ParametersJSON 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

ParametersJSON Schema
NameRequiredDescription
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'.

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • Changedfestival_details7 fields changed
      • 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"
+}
    • Changedfestivals_in_month9 fields changed
      • changedInput schema / properties / month / description
        Previous value: -"The month as a number."New value: +"Calendar month 1-12 (1 = January, 12 = December)"
      • addedInput schema / properties / month / maximum
        Added value: +12
      • addedInput schema / properties / month / minimum
        Added value: +1
      • changedInput schema / properties / month / type
        Previous value: -"number"New value: +"integer"
      • 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": {
+    "festivals": {
+      "description": "Festivals in that month, sorted by date (may be empty).",
+      "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"
+    },
+    "month": {
+      "description": "The calendar month that was searched, 1-12.",
+      "type": "integer"
+    },
+    "year": {
+      "description": "The year that was searched.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "year",
+    "month",
+    "festivals"
+  ],
+  "type": "object"
+}
    • Changedlist_festivals5 fields changed
      • 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"
+}
    • Changednext_festival3 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. 4 tool updates
    • Changedfestival_details1 field changed
      • 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
    • Changedfestivals_in_month1 field changed
      • changedOutput schema / (root)
        Previous value: -{
-  "properties": {
-    "festivals": {
-      "description": "List of festivals occurring in the specified month and year.",
-      "items": {
-        "properties": {
-          "date": {
-            "description": "The date on which the festival occurs.",
-            "format": "date",
-            "type": "string"
-          },
-          "details": {
-            "description": "Additional details about 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"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "month": {
-      "description": "The month for which the festivals are retrieved.",
-      "type": "number"
-    },
-    "year": {
-      "description": "The year for which the festivals are retrieved.",
-      "type": "number"
-    }
-  },
-  "required": [
-    "month",
-    "year",
-    "festivals"
-  ],
-  "type": "object"
-}New value: +null
    • Changedlist_festivals1 field changed
      • 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
    • Changednext_festival1 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. 4 tool updates
    • Changedfestival_details3 fields changed
      • 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"
+}
    • Changedfestivals_in_month3 fields changed
      • addedInput schema / properties / month / description
        Added value: +"The month as a number."
      • addedInput schema / properties / year / description
        Added value: +"The year as a number."
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "properties": {
+    "festivals": {
+      "description": "List of festivals occurring in the specified month and year.",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "The date on which the festival occurs.",
+            "format": "date",
+            "type": "string"
+          },
+          "details": {
+            "description": "Additional details about 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"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "month": {
+      "description": "The month for which the festivals are retrieved.",
+      "type": "number"
+    },
+    "year": {
+      "description": "The year for which the festivals are retrieved.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "month",
+    "year",
+    "festivals"
+  ],
+  "type": "object"
+}
    • Changedlist_festivals2 fields changed
      • 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"
+}
    • Changednext_festival2 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. 4 tool updates
    • First observedfestival_details
    • First observedfestivals_in_month
    • First observedlist_festivals
    • First observednext_festival

Related MCP Connectors

Related MCP Servers

  • panchangam-mcp

    vgnshlvnz
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables retrieval of the Hindu almanac for a given date and place, including tithi, nakshatra, yoga, karana, vaara, sunrise/sunset, and auspicious or inauspicious muhurta periods.
    -

  • mcp-indian-astrology

    Dinesh-Gahlot
    A
    license
    C
    quality
    C
    maintenance
    Enables AI assistants to access Indian Vedic astrology services including Panchang, Kundli, matchmaking, and festivals through natural language.
    128
    MIT

  • Kundlit Vedic Astrology

    puru991
    A
    license
    A
    quality
    C
    maintenance
    Hosted Streamable HTTP MCP server for Vedic astrology: panchang, kundali (birth chart), matchmaking, dashas, doshas, muhurta and 16 tools computed by a precision astronomy engine.
    17
    18 npm
    MIT

  • vedic-muhurta-mcp

    mrpkk
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to find auspicious windows for launches, travel, weddings, purchases, publications, and other events using Vedic electional astrology, and to retrieve panchanga, planetary hours, and Rahu Kala.
    MIT
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