Japan Public Holidays

Business days

business_days

Read-onlyIdempotent

Count business days between start and end (inclusive), or find the date that is N business days after start (add=N; negative N goes backward; start itself is not counted). Business day = weekday that is not a national holiday. Set year_end_closed to also skip 12/29-1/3. With country, uses that country's weekend days, holidays and make-up workdays.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`add`	No	Move this many business days from start.
`end`	No	Count up to this date (inclusive).
`start`	Yes	YYYY-MM-DD
`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
`year_end_closed`	No	Japan only.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 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"
+}

addedInput schema / properties / year_end_closed / description
```
Added value: +"Japan only."
```

First observedOct 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, non-open-world behavior, so the safety profile is covered. The description adds genuine semantic context: the definition of a business day, the 12/29-1/3 year-end closure, and that country switches weekend days, holidays and make-up workdays.

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?

One dense paragraph, front-loaded with the two operating modes before the supporting definitions. Every sentence carries information, though the packed clauses make it slightly heavier than ideal.

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, the description must imply return values, and it does so reasonably: a count for the end mode and a date for the add mode. It stops short of stating the exact return format (e.g., date string format), a minor gap for a 6-parameter 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 100%, so the baseline is 3, but the description adds meaning beyond the schema: it clarifies that 'add' can be negative, that 'start' is not counted, and that 'country' controls weekend days, holidays and make-up workdays — details the schema hints at only briefly.

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 two specific operations over a named resource: counting business days between start and end, and finding the date N business days from start. This is unmistakably distinct from list_holidays or find_long_weekends in intent, but no sibling is explicitly named, so it earns a 4 rather than 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 explains how to select each mode: provide 'end' to count, or 'add=N' to shift forward/backward, with negative N going backward and start itself excluded. However, it offers no guidance on when to prefer this tool over check_dates or the other siblings.

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?