euroref — European government reference data

get_public_holidays_worldwide

Read-onlyIdempotent

FREE with any API key, including the free key by email (https://euroref.dev/free-key). Same as get_public_holidays, but for every country across all seven brands, not only European. Unmetered: never counts against the key's allowance. Pass api_key, or send the key as the X-API-Key header on /mcp.

Input Schema

TableJSON Schema

Name	Required	Description
`api_key`	No	Any valid API key. Optional when the key is sent as the X-API-Key header on /mcp.
`country`	Yes	ISO country code, any covered country
`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

TableJSON 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"
+]
```
AddedOct 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: it is free and unmetered (never counts against the allowance) and documents the two auth paths (api_key param or X-API-Key header). No return-format detail, but the output schema covers that.

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?

Four short sentences, with the strongest selection signal (free/unmetered) front-loaded and the sibling comparison immediately after. The free-key URL is slightly promotional but functional, and no sentence is wasted.

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?

An output schema exists, so return values need not be described. Combined with annotations and the description's cost, auth and scope coverage, an agent has what it needs to call the tool correctly; only a note on behavior with an invalid/unsupported country would improve it.

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 enum country list and the subdivision semantics are already fully documented by the schema. The description's auth note about api_key largely repeats the schema's own api_key description, adding no new meaning for country or subdivision. 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 states the resource (public holidays) and its distinguishing scope (every country across all seven brands, not only European) and explicitly names the sibling get_public_holidays as the narrower variant. The verb is only implied via 'Same as get_public_holidays', but the resource and scope are unambiguous and the agent can separate it from siblings.

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?

It clearly frames when to pick this over get_public_holidays (worldwide vs European-only) and notes the cost condition (free/unmetered with any key). It stops short of explicit exclusions or a full alternative-selection rule, but the routing signal is clear.

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

All euroref — European government 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?