Japan Business Day

is_business_day

Check whether a date is a business day in Japan (official Cabinet Office holiday data). Returns holiday name (JA/EN) and next/previous business day. Price: $0.005 USDC via x402.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>"
    },
    "name": "is_business_day"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes	Date in YYYY-MM-DD. Supported range 1955-01-01..2027-12-31
`calendar`	No	national (default): weekends + national holidays. bank: also Dec 31 - Jan 3 bank holidays

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 26, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses the data source, return elements (holiday name in JA/EN and next/previous business day), and the price ($0.005 USDC via x402). For a read-only check, this is solid context. It does not mention rate limits or side effects, but none are apparent.

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?

Two efficient sentences: the first states the purpose and data source, the second covers return value and price. No filler, all information is relevant, and the core action is front-loaded.

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?

For a simple 2-parameter tool with no annotations and no output schema, the description covers the essentials: purpose, data source, return content, and cost. It does not detail the response shape or error handling, but the schema covers input constraints. It is complete enough for an agent to invoke correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents the 'date' format/range and 'calendar' enum/default. The description adds no extra parameter semantics beyond implying the date is what gets checked. It does not clarify edge cases or how the calendar parameter affects the return. Baseline 3 is appropriate.

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 clearly states a specific verb ('Check') and resource ('whether a date is a business day in Japan') and names the data source ('official Cabinet Office holiday data'). It also mentions the return content, which distinguishes it from siblings like list_holidays or add_business_days. The agent can tell what this tool does without opening the schema.

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

Usage Guidelines3/5

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

The description gives the context ('check whether a date is a business day in Japan') but does not explicitly discuss when to use this tool versus alternatives like is_business_day_free or add_business_days. It does not mention exclusions or trade-offs (e.g., the paid tier vs free version). Usage is implied rather than directly guided.

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

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