DatoQA — Official Public Holidays

catalog

Read-onlyIdempotent

Inspect this connection’s scope, tools and access policy. With no arguments returns the usual catalog. On the general or economy connection, optionally supply report_countries (1–10 World Bank codes) for a FREE live preview of the optional paid country comparison: population/GDP/inflation by default, or up to six selected historical indicators over ten years, aligned JSON and CSV, definitions and source evidence. Preview reports price, missing cells, availability and the exact HTTP purchase path; it never signs or pays. Existing data tools remain free. Buying requires an authorized x402 HTTP client, not just MCP. Source/schema checks are not independent factual verification.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`language`	No	Response metadata language, English by default or French; original source definitions and notes remain preserved.	en
`report_to`	No	Inclusive last observation year, no later than the last completed calendar year. Supply with report_from and report_indicators; missing observations block purchase.
`report_from`	No	Inclusive first observation year for a custom country preview. Supply with report_to and report_indicators; at most ten years, from 1960 onward.
`report_countries`	No	Optional free preview for these distinct World Bank country codes, e.g. FRA, DEU, ESP. General/economy connections only.
`report_indicators`	No	Custom historical comparison: select up to six of the 22 WDI indicators. Supply report_from and report_to together, up to ten years. Missing cells block payment.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`title`	No
`tools`	No
`profile`	No
`version`	No
`capabilities`	No
`available_records`	No
`independently_verified`	No	Official-source checks are not independent factual corroboration.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / language / description

Added value: +"Response metadata language, English by default or French; original source definitions and notes remain preserved."

addedInput schema / properties / report_from / description

Added value: +"Inclusive first observation year for a custom country preview. Supply with report_to and report_indicators; at most ten years, from 1960 onward."

addedInput schema / properties / report_to / description

Added value: +"Inclusive last observation year, no later than the last completed calendar year. Supply with report_from and report_indicators; missing observations block purchase."

Changed3 schema fields changedSep 28, 2026

addedInput schema / properties / report_from

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 1960,
+  "type": "integer"
+}

addedInput schema / properties / report_indicators

Added value: +{
+  "description": "Custom historical comparison: select up to six of the 22 WDI indicators. Supply report_from and report_to together, up to ten years. Missing cells block payment.",
+  "items": {
+    "enum": [
+      "population",
+      "gdp",
+      "gdp_per_capita",
+      "gdp_real",
+      "gdp_growth",
+      "inflation",
+      "life_expectancy",
+      "fertility",
+      "urban_population",
+      "internet_users",
+      "electricity_access",
+      "unemployment",
+      "renewable_energy",
+      "forest_area",
+      "agricultural_land",
+      "trade",
+      "exports",
+      "imports",
+      "infant_mortality",
+      "basic_drinking_water",
+      "basic_sanitation",
+      "primary_completion"
+    ],
+    "type": "string"
+  },
+  "maxItems": 6,
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / report_to

Added value: +{
+  "maximum": 2025,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changed3 schema fields changedSep 28, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / language

Added value: +{
+  "default": "en",
+  "enum": [
+    "en",
+    "fr"
+  ],
+  "type": "string"
+}

addedInput schema / properties / report_countries

Added value: +{
+  "description": "Optional free preview for these distinct World Bank country codes, e.g. FRA, DEU, ESP. General/economy connections only.",
+  "items": {
+    "pattern": "^[A-Z0-9]{3}$",
+    "type": "string"
+  },
+  "maxItems": 10,
+  "minItems": 1,
+  "type": "array"
+}

Changed1 schema field changedSep 28, 2026

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedSep 27, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description layers on real behavioral context the structured fields can't convey: the preview 'never signs or pays,' missing cells block purchase, reports expose price/availability/HTTP purchase path, and source/schema checks are not independent factual verification. This is valuable disclosure beyond annotations.

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?

Front-loads the core purpose and keeps every sentence informative, but the second half is a dense run-on covering preview outputs, pricing, purchase path, and caveats. Slightly crowded, yet nothing is pure filler.

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 an unusual dual-purpose tool (catalog inspection plus paid-data preview) with an output schema already covering return values, the description supplies the needed context: scope, the free-vs-paid boundary, preview contents, payment prerequisites, and an analytical caveat.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter semantics the schema doesn't: report_from/report_to must be supplied together with report_indicators, missing observations block purchase, and report_countries triggers a free preview only on general/economy connections. That is meaningful added meaning.

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 concrete verb+resource ('Inspect this connection's scope, tools and access policy') and adds a second, clearly described capability (free country-comparison preview). It implies differentiation from the data siblings by noting 'Existing data tools remain free,' but never names a sibling, so it stops short of a 5.

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?

Gives clear when-to-use guidance: call with no arguments for the plain catalog, or supply report_countries on the general/economy connection for a preview, and explicitly states buying needs an authorized x402 HTTP client 'not just MCP.' No explicit when-NOT-to-use beyond that constraint, so not a 5.

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

All DatoQA — Official Public Holidays 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?