Japan Public Holidays

List holidays

list_holidays

Read-onlyIdempotent

List Japanese national holidays for a year, or between from and to. With no arguments, lists the next 10 holidays from today (Japan time). With country, lists that country's public holidays (and make-up workdays, if any).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No	End date (inclusive).
`from`	No	Start date (default: today in Japan).
`year`	No
`limit`	No
`region`	No	Outside Japan: state/province code (ISO 3166-2 suffix, e.g. CA for California) to include regional holidays.
`country`	No	ISO 3166-1 alpha-2 country code (e.g. JP, US, CN, GB). Default JP.	JP

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

addedInput schema / properties / country

Added value: +{
+  "default": "JP",
+  "description": "ISO 3166-1 alpha-2 country code (e.g. JP, US, CN, GB). Default JP.",
+  "pattern": "^[A-Za-z]{2}$",
+  "type": "string"
+}

addedInput schema / properties / region

Added value: +{
+  "description": "Outside Japan: state/province code (ISO 3166-2 suffix, e.g. CA for California) to include regional holidays.",
+  "type": "string"
+}

First observedOct 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description still adds real value beyond them: the implicit default of 10 results from today in Japan time, the JP default country, and the fact that make-up workdays may be included.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the primary purpose and then the default/override behaviors. Every sentence carries information an agent needs; nothing is padded.

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?

With no output schema and 6 optional parameters, the description covers the main invocation modes and defaults well. It omits how year interacts with from/to, the limit maximum of 200, and the return shape, but those are minor for a read-only listing 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?

Schema coverage is 67%, with from/to/country/region documented but year and limit bare. The description compensates by revealing the implicit default limit ('next 10 holidays') and the default country behavior, which are not stated anywhere in the schema.

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 a specific verb and resource ('List Japanese national holidays') and defines the scope precisely, including the country override. It doesn't explicitly name or differentiate from siblings like business_days or find_long_weekends, so it falls 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?

It clearly describes the three invocation modes: no arguments (next 10 holidays from today, Japan time), year/from-to ranges, and country selection. That is strong context for choosing how to call it, though it never states when to prefer this over the sibling date tools or any exclusions.

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

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