Skip to main content
Glama

holidays

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Holidays

get_holidays
Read-onlyIdempotent

Get all public holidays for a country and year. Returns holiday names and dates. Provide country code (e.g., "US", "GB", "DE") and year.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesThe year to retrieve holidays for (e.g., 2025)
country_codeYesISO 3166-1 alpha-2 country code (e.g., US, GB, DE, FR)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesThe year for which holidays were retrieved
holidaysYesList of public holidays for the country and year
country_codeYesISO 3166-1 alpha-2 country code in uppercase

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country_code": "US",
+    "year": 2025
+  },
+  {
+    "country_code": "DE",
+    "year": 2024
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "country_code": {
+      "description": "ISO 3166-1 alpha-2 country code in uppercase",
+      "type": "string"
+    },
+    "holidays": {
+      "description": "List of public holidays for the country and year",
+      "items": {
+        "properties": {
+          "counties": {
+            "description": "Specific counties/regions where holiday is observed",
+            "items": {
+              "type": "string"
+            },
+            "type": [
+              "array",
+              "null"
+            ]
+          },
+          "date": {
+            "description": "Holiday date (ISO format)",
+            "type": "string"
+          },
+          "global": {
+            "description": "Whether holiday is observed globally in the country",
+            "type": "boolean"
+          },
+          "local_name": {
+            "description": "Holiday name in local language",
+            "type": "string"
+          },
+          "name": {
+            "description": "Holiday name in English",
+            "type": "string"
+          },
+          "types": {
+            "description": "Holiday types (e.g., Public, Bank, School)",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "date",
+          "name",
+          "local_name",
+          "global",
+          "counties",
+          "types"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "year": {
+      "description": "The year for which holidays were retrieved",
+      "type": "number"
+    }
+  },
+  "required": [
+    "country_code",
+    "year",
+    "holidays"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "country_code": "US",
-    "year": 2025
-  },
-  {
-    "country_code": "DE",
-    "year": 2025
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "count": {
-      "description": "Total number of holidays returned",
-      "type": "number"
-    },
-    "country_code": {
-      "description": "ISO 3166-1 alpha-2 country code in uppercase",
-      "type": "string"
-    },
-    "holidays": {
-      "description": "List of public holidays for the country and year",
-      "items": {
-        "properties": {
-          "counties": {
-            "description": "List of counties/regions where holiday applies, or null if global",
-            "items": {
-              "type": "string"
-            },
-            "type": [
-              "array",
-              "null"
-            ]
-          },
-          "date": {
-            "description": "Holiday date in YYYY-MM-DD format",
-            "type": "string"
-          },
-          "fixed": {
-            "description": "Whether holiday is on a fixed date each year",
-            "type": "boolean"
-          },
-          "global": {
-            "description": "Whether holiday is observed globally across the country",
-            "type": "boolean"
-          },
-          "local_name": {
-            "description": "Holiday name in local language",
-            "type": "string"
-          },
-          "name": {
-            "description": "Holiday name in English",
-            "type": "string"
-          },
-          "types": {
-            "description": "Holiday types (e.g., public, bank, school)",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          }
-        },
-        "required": [
-          "date",
-          "name",
-          "local_name",
-          "global",
-          "counties",
-          "types",
-          "fixed"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "year": {
-      "description": "The year requested",
-      "type": "number"
-    }
-  },
-  "required": [
-    "year",
-    "country_code",
-    "count",
-    "holidays"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of holidays returned",
+      "type": "number"
+    },
+    "country_code": {
+      "description": "ISO 3166-1 alpha-2 country code in uppercase",
+      "type": "string"
+    },
+    "holidays": {
+      "description": "List of public holidays for the country and year",
+      "items": {
+        "properties": {
+          "counties": {
+            "description": "List of counties/regions where holiday applies, or null if global",
+            "items": {
+              "type": "string"
+            },
+            "type": [
+              "array",
+              "null"
+            ]
+          },
+          "date": {
+            "description": "Holiday date in YYYY-MM-DD format",
+            "type": "string"
+          },
+          "fixed": {
+            "description": "Whether holiday is on a fixed date each year",
+            "type": "boolean"
+          },
+          "global": {
+            "description": "Whether holiday is observed globally across the country",
+            "type": "boolean"
+          },
+          "local_name": {
+            "description": "Holiday name in local language",
+            "type": "string"
+          },
+          "name": {
+            "description": "Holiday name in English",
+            "type": "string"
+          },
+          "types": {
+            "description": "Holiday types (e.g., public, bank, school)",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "date",
+          "name",
+          "local_name",
+          "global",
+          "counties",
+          "types",
+          "fixed"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "year": {
+      "description": "The year requested",
+      "type": "number"
+    }
+  },
+  "required": [
+    "year",
+    "country_code",
+    "count",
+    "holidays"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country_code": "US",
+    "year": 2025
+  },
+  {
+    "country_code": "DE",
+    "year": 2025
+  }
+]
  5. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is well covered. The description adds that it returns all holidays and includes names/dates, but doesn't discuss edge cases, errors, or rate limits. This is adequate but minimal beyond annotational safety.

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?

The description is two sentences long and front-loads the core purpose ('Get all public holidays for a country and year') before noting the return value and required inputs. Every word earns its place, and there is no redundancy.

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 read-only tool with only two parameters, complete schema descriptions, a strong annotation set, and an output schema present, the description adequately covers the core behavior and return summary. It doesn't need to explain return structure in detail.

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 input schema already fully documents both parameters with descriptions and examples, giving 100% coverage. The description merely restates the need for country code and year without adding new meaning, so it earns the baseline score.

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?

The description uses a specific verb ('Get') and resource ('all public holidays for a country and year'), clearly distinguishing it from siblings like next_holidays or is_today_holiday by scope. It also states the return content (holiday names and dates), making the tool's purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool: to retrieve all public holidays for a specific country and year. However, it doesn't explicitly mention alternatives or exclusions, such as 'for upcoming holidays use next_holidays', so it falls short of explicit guidance.

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

All holidays toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources