Business Days and Holidays

List public and school holidays

list_holidays

Read-onlyIdempotent

Use this when the user asks which public holidays, bank holidays or school holidays a country, state or province has in a year, for example "is Monday a bank holiday in Bavaria?", "public holidays in Vietnam in 2027" or "school holidays in Bavaria". Pass the country code and the year, a region when the user names one, and kind school for school holidays, which are published for a limited set of countries. Public holidays come back with the date, weekday, English and local name, whether they apply nationwide or in listed regions, and whether they are a day off. Do not use it for religious or cultural festival dates without a country, trading-day calendars, or company holidays.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	public (default) for public holidays, or school for school holidays, which exist for a limited set of countries.
`year`	Yes	Calendar year, for example 2027.
`region`	No	State, province or nation within the country, as a subdivision code such as DE-BY or BY (Bavaria), GB-SCT (Scotland), US-CA or AU-NSW. Optional.
`country`	Yes	Two-letter ISO 3166-1 country code whose holidays apply, such as US, GB, DE, AU or VN.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	Yes
`note`	No
`year`	Yes
`region`	No
`source`	Yes
`country`	Yes
`publicHolidays`	No
`schoolHolidays`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 3, 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, openWorld and non-destructive, so safety is covered. The description adds real context the annotations do not: school holidays exist only for a limited set of countries, and the tool struggles with festival dates lacking a country. A minor gap remains around coverage/pagination limits, but the disclosure is solid.

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?

Well front-loaded: trigger and examples first, then parameter guidance, then a negative-usage sentence. Slightly dense, and the enumeration of return fields partially restates what the output schema already conveys, but every part is relevant.

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?

With an output schema present, the description need not explain return values, and annotations carry the safety profile. Given the tool's moderate complexity, the description still supplies triggers, examples, parameter routing, and coverage caveats, leaving nothing an agent needs missing.

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. The description goes beyond the schema by explaining when to supply region (only when the user names one) and that kind=school is restricted to a limited country set, giving conditional usage semantics the schema alone does not.

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?

States a specific verb and resource (list public and school holidays) with clear scope: country/state/province and year. It is plainly distinguishable from the sibling business-day tools, which deal with counting/adding working days rather than holiday calendars.

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?

Opens with an explicit trigger ('Use this when the user asks which public holidays...') backed by concrete example queries, and closes with explicit exclusions (religious/cultural festivals without a country, trading-day calendars, company holidays). This is textbook when/when-not guidance.

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

All Business Days and 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?