Skip to main content
Glama

holidays

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Next Holidays

next_holidays
Read-onlyIdempotent

Get upcoming public holidays from today onward for a country. Returns holiday names and dates. Provide country code (e.g., "US", "GB", "DE").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_codeYesISO 3166-1 alpha-2 country code (e.g., US, GB, DE, FR)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_codeYesISO 3166-1 alpha-2 country code in uppercase
upcoming_holidaysYesList of upcoming public holidays from today onward

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "country_code": {
+      "description": "ISO 3166-1 alpha-2 country code in uppercase",
+      "type": "string"
+    },
+    "upcoming_holidays": {
+      "description": "List of upcoming public holidays from today onward",
+      "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"
+    }
+  },
+  "required": [
+    "country_code",
+    "upcoming_holidays"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country_code": "FR"
+  },
+  {
+    "country_code": "JP"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations by specifying the temporal window ('from today onward') and that it returns names and dates, which helps the agent understand the exact output scope.

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 concise sentences that are front-loaded with the core purpose and immediately provide the required parameter format. No wasted words or repetition.

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 one-parameter tool with a complete output schema and comprehensive annotations, the description is fully sufficient. It covers what the tool does, the specific time scope, and the required input format, making it complete for an agent to invoke correctly.

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 schema has 100% coverage for the single parameter 'country_code' with a clear description. The description repeats the parameter instruction ('Provide country code') without adding new semantics beyond what the schema already provides, so it meets the baseline of 3.

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 clearly states a specific verb ('Get'), a resource ('upcoming public holidays'), and a scope ('from today onward for a country'). This distinguishes it from siblings like 'is_today_holiday' (single day) and 'get_holidays' (likely broader range) by emphasizing the future time window.

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 implies when to use this tool by specifying 'from today onward', which signals it is for future holidays. However, it does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to choose this over a general holiday list tool.

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