jp-business-calendar-mcp

Overview Schema Source Related Servers Discussions Admin

next_business_day

Determine a date offset by business days from a starting date, skipping weekends and Japanese holidays. Supports forward and backward offsets.

Instructions

指定日から days 営業日後（土日祝を除く）を返す。days に負数で過去方向も可。

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": "next_business_day"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes
`days`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description mentions that the tool excludes weekends and holidays and supports negative days. However, it does not specify which holiday calendar is used, how zero days are handled, or what happens if the input date is a holiday. With no annotations provided, the description should disclose more behavioral details.

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?

The description consists of two concise sentences in Japanese. The first sentence defines the core function, and the second adds the negative-days capability. No extraneous information is included.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description explains the business logic, it lacks details on the return value format (e.g., date string type), zero-day behavior, and holiday calendar. Given no output schema and no annotations, these omissions reduce completeness for an agent to use the tool 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?

The description adds meaning beyond the input schema by clarifying that 'days' refers to business days excluding holidays and that negative values are supported. However, it does not specify the expected date format (e.g., YYYY-MM-DD) or explain that the 'date' parameter is the starting point. Schema description coverage is 0%, so the description partially compensates but is not complete.

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 the tool returns a date that is 'days' business days after a specified date, excluding weekends and holidays, and allows negative values for past dates. This specific verb-resource combination ('returns date after business days') distinguishes it from siblings like 'business_days_between' (counts days) and 'is_holiday' (checks if date is holiday).

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 explains core usage (adding/subtracting business days) and mentions negative days for past direction, but does not explicitly guide when to use this tool versus alternatives such as 'days_until' or 'payment_date'. Usage context is implied rather than explicitly stated.

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

Deploy Server