reference-data

get_public_holidays

Read-onlyIdempotent

FREE. Official public-holiday calendar for a supported country, including gazetted movable holidays, with the official government source cited. Some countries also carry sub-national calendars (e.g. the German Laender): the subdivisions field lists them, and passing subdivision (ISO 3166-2, e.g. 'DE-BY') returns the national calendar merged with that region's statutory days.

Input Schema

Name	Required	Description	Default
`country`	Yes	ISO country code
`subdivision`	No	Optional ISO 3166-2 region code (e.g. 'DE-BY'). Returns national + that region's statutory holidays, each tagged national/regional. Omit for the national calendar.

Output Schema

Name	Required	Description
`unit`	No
`error`	No	Present on a free refusal or error; no charge
`notes`	No
`stale`	No
`value`	No
`series`	No
`source`	No
`country`	No
`no_charge`	No
`price_usd`	No
`confidence`	No
`disclaimer`	No
`how_to_pay`	No
`bind_series`	No
`explanation`	No
`label_basis`	No	Inputs and the rule ids that produced the two labels
`subdivision`	No
`x_next_bind`	No
`http_endpoint`	No
`coverage_label`	No	How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules
`effective_from`	No
`last_confirmed`	No
`confidence_label`	No	Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules
`payment_required`	No	true when the call needs payment; how_to_pay explains x402 or card
`available_subdivisions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 17, 2026
- removedOutput schema / properties / label_basis / properties / source_type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / label_basis / properties / source_type / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / label_basis / properties / verification_age_days / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / label_basis / properties / verification_age_days / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed3 schema fields changedOct 13, 2026

addedOutput schema / properties / confidence_label

Added value: +{
+  "description": "Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules",
+  "enum": [
+    "high",
+    "medium",
+    "low"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / coverage_label

Added value: +{
+  "description": "How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules",
+  "enum": [
+    "ready",
+    "partial",
+    "gap"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / label_basis

Added value: +{
+  "additionalProperties": {},
+  "description": "Inputs and the rule ids that produced the two labels",
+  "properties": {
+    "confidence_reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "coverage_reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "inputs": {
+      "items": {},
+      "type": "array"
+    },
+    "rules": {
+      "type": "string"
+    },
+    "rules_version": {
+      "type": "string"
+    },
+    "source_type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "stale": {
+      "type": "boolean"
+    },
+    "verification_age_days": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "Holiday calendar series with cited source; with subdivision, merged national+regional days",
+  "properties": {
+    "available_subdivisions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "bind_series": {},
+    "confidence": {},
+    "country": {
+      "type": "string"
+    },
+    "disclaimer": {},
+    "effective_from": {},
+    "error": {
+      "description": "Present on a free refusal or error; no charge"
+    },
+    "explanation": {},
+    "how_to_pay": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "http_endpoint": {
+      "type": "string"
+    },
+    "last_confirmed": {},
+    "no_charge": {
+      "type": "boolean"
+    },
+    "notes": {},
+    "payment_required": {
+      "description": "true when the call needs payment; how_to_pay explains x402 or card",
+      "type": "boolean"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "series": {
+      "type": "string"
+    },
+    "source": {},
+    "stale": {
+      "type": "boolean"
+    },
+    "subdivision": {},
+    "unit": {},
+    "value": {},
+    "x_next_bind": {}
+  },
+  "type": "object"
+}

Changed1 schema field changedJul 28, 2026

addedInput schema / properties / subdivision

Added value: +{
+  "description": "Optional ISO 3166-2 region code (e.g. 'DE-BY'). Returns national + that region's statutory holidays, each tagged national/regional. Omit for the national calendar.",
+  "type": "string"
+}

Changed1 schema field changedJul 24, 2026

changedInput schema / properties / country / enum

Previous value: -[
-  "ar",
-  "bb",
-  "bo",
-  "br",
-  "bz",
-  "cl",
-  "co",
-  "cr",
-  "do",
-  "ec",
-  "gt",
-  "hn",
-  "jm",
-  "mx",
-  "ni",
-  "pa",
-  "pe",
-  "py",
-  "sv",
-  "tt",
-  "uy"
-]New value: +[
+  "ar",
+  "bb",
+  "bo",
+  "br",
+  "bz",
+  "cl",
+  "co",
+  "cr",
+  "do",
+  "ec",
+  "gt",
+  "gy",
+  "hn",
+  "jm",
+  "mx",
+  "ni",
+  "pa",
+  "pe",
+  "py",
+  "sv",
+  "tt",
+  "uy"
+]

Changed1 schema field changedJul 24, 2026

changedInput schema / properties / country / enum

Previous value: -[
-  "ar",
-  "bo",
-  "br",
-  "cl",
-  "co",
-  "cr",
-  "do",
-  "ec",
-  "gt",
-  "hn",
-  "mx",
-  "pa",
-  "pe",
-  "py",
-  "sv",
-  "uy"
-]New value: +[
+  "ar",
+  "bb",
+  "bo",
+  "br",
+  "bz",
+  "cl",
+  "co",
+  "cr",
+  "do",
+  "ec",
+  "gt",
+  "hn",
+  "jm",
+  "mx",
+  "ni",
+  "pa",
+  "pe",
+  "py",
+  "sv",
+  "tt",
+  "uy"
+]

Changed1 schema field changedJul 20, 2026

changedInput schema / properties / country / enum

Previous value: -[
-  "ar",
-  "br",
-  "cl",
-  "co",
-  "cr",
-  "do",
-  "ec",
-  "gt",
-  "mx",
-  "pe",
-  "py",
-  "uy"
-]New value: +[
+  "ar",
+  "bo",
+  "br",
+  "cl",
+  "co",
+  "cr",
+  "do",
+  "ec",
+  "gt",
+  "hn",
+  "mx",
+  "pa",
+  "pe",
+  "py",
+  "sv",
+  "uy"
+]

First observedJul 17, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the description's job is to add context — and it does: cost ('FREE'), data provenance ('official government source cited'), coverage caveat ('gazetted movable holidays'), and the merge semantics of a regional request. It does not discuss rate limits or response shape, but the output schema covers the latter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with cost and purpose, with the subdivision mechanics in the second. Dense but no wasted filler; the parenthetical '(e.g. the German Laender)' is arguably the only removable clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema carries return-value detail, so that gap is excused, but the description's worked example ('DE-BY', German Laender) is not among the enumerated country codes in the schema, which could mislead an agent into requesting an unsupported subdivision. That inconsistency plus the absent alternative-tool guidance leaves it adequate but not 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?

Schema description coverage is 100%, so both parameters are already documented; the description's ISO 3166-2 example and national+regional merge behavior largely restate the schema text for `subdivision`. Only the pointer to a `subdivisions` field in the response adds marginal value, so the baseline 3 applies.

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?

States a specific verb+resource ('Official public-holiday calendar for a supported country') and scopes it to a single country, which implicitly separates it from the sibling get_public_holidays_worldwide. It never names that sibling, so the differentiation is left to inference rather than stated.

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?

Usage is only implied: 'for a supported country' and 'Omit for the national calendar' tell the agent when to pass subdivision, but there is no when-to-use guidance and no routing to get_public_holidays_worldwide or get_calendar for multi-country or other calendar needs.

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

All reference-data tools Inspect

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

Need Help?