DatoQA

list_holiday_regions

Read-onlyIdempotent

Discover available public-holiday calendars and exact region ids, published years, source kind and freshness. Includes FR/UK/HK government feeds and international OpenHolidays curated entries. Use when country/region/year coverage is unknown; otherwise call get_public_holidays directly. Configured calendars are not proof of available data. International coverage is incomplete.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_holiday_regions"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`notice`	Yes
`regions`	Yes
`endpoint`	Yes
`region_count`	Yes
`count_meaning`	Yes
`configured_regions`	Yes
`source_event_count`	Yes
`independently_verified`	Yes	Official-source checks are not independent factual corroboration.
`refresh_interval_seconds`	Yes
`max_collection_age_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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"

Changed2 schema fields changedSep 27, 2026
- addedOutput schema / properties / regions / items / properties / date_confirmation
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / regions / items / properties / source_kind
```
Added value: +{
+  "type": "string"
+}
```
First observedSep 27, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavioral caveats: 'Configured calendars are not proof of available data' and 'International coverage is incomplete,' which warn about data-coverage semantics an agent cannot infer from annotations or schema. It stops short of describing pagination or output shape, but the output schema exists.

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 sentences, all earning their place, with the primary purpose front-loaded before the routing guidance and caveats. Slightly dense but no filler 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?

Combined with an output schema (which carries return-value detail) and annotations (which carry the safety profile), the description supplies everything else an agent needs: purpose, selection rule, named alternative, and data-coverage caveats. Nothing material is missing for a zero-parameter catalog tool.

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?

The tool takes zero parameters and the input schema is an empty object, so the baseline is 4. There is nothing parameter-related for the description to compensate for, and it correctly implies a no-argument discovery call.

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 names a specific verb (Discover) and resource (available public-holiday calendars and exact region ids, published years, source kind, freshness), and explicitly distinguishes itself from the sibling get_public_holidays. An agent can immediately tell this is a catalog-discovery tool rather than a data-fetch tool.

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

Usage Guidelines5/5

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

It states the exact condition for use ('when country/region/year coverage is unknown') and routes the agent to the alternative ('otherwise call get_public_holidays directly'). This is explicit when/when-not plus the named alternative, the top of the scale.

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

All DatoQA 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?