Skip to main content
Glama

holidays

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Is Today Holiday

is_today_holiday
Read-onlyIdempotent

Check if today is a public holiday in a given country. Returns whether it's a holiday and the holiday name if applicable. Provide country code (e.g., "US", "GB").

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
is_holidayYesWhether today is a public holiday in the country
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"
+  },
+  {
+    "country_code": "GB"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "country_code": {
+      "description": "ISO 3166-1 alpha-2 country code in uppercase",
+      "type": "string"
+    },
+    "is_holiday": {
+      "description": "Whether today is a public holiday in the country",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "country_code",
+    "is_holiday"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "country_code": "US"
-  },
-  {
-    "country_code": "GB"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "country_code": {
-      "description": "ISO 3166-1 alpha-2 country code in uppercase",
-      "type": "string"
-    },
-    "is_holiday": {
-      "description": "True if today is a public holiday in the country, false otherwise",
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "country_code",
-    "is_holiday"
-  ],
-  "type": "object"
-}New value: +null
  3. 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"
+    },
+    "is_holiday": {
+      "description": "True if today is a public holiday in the country, false otherwise",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "country_code",
+    "is_holiday"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country_code": "US"
+  },
+  {
+    "country_code": "GB"
+  }
+]
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds that it returns whether it's a holiday and the name, but this is minimal and does not disclose additional behavioral traits beyond what annotations provide.

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, front-loaded with the main purpose, and includes a concrete example. No unnecessary words or redundancy beyond the schema repetition, making it highly concise and well-structured.

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?

This is a simple tool with one parameter, full schema coverage, and an output schema. The description covers the essential purpose and input format. It does not clarify differences from sibling holiday tools, but given the simplicity and rich structured data, it is sufficiently complete.

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 fully describes the country_code parameter with ISO 3166-1 alpha-2 format and examples. The description repeats this with 'Provide country code (e.g., "US", "GB")', adding no new meaning beyond the schema. Thus baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: checking if today is a public holiday in a given country, with a specific verb (check) and resource (holiday). It does not explicitly distinguish from sibling tools like get_holidays or next_holidays, but the 'today' scope provides implicit distinction.

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

Usage Guidelines3/5

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

The description specifies the usage context ('Check if today is a public holiday') and provides an example of the input. However, it does not mention when not to use this tool or suggest alternatives, leaving the usage guidance implied rather than explicit.

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