Skip to main content
Glama

Japan Calendar

Add Japanese business days

add_business_days
Read-onlyIdempotent

Move forward (or backward with a negative number) by N business days in Japan, skipping weekends and national holidays. Use for due dates such as "within 5 business 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>",
      "days": "<days>"
    },
    "name": "add_business_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesStart date, YYYY-MM-DD (not counted)
daysYesBusiness days to add; negative goes back
year_end_breakNoAlso treat Dec 31 - Jan 3 as non-business days (common for banks and most Japanese companies). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the burden is lower. The description adds meaningful behavior beyond them: weekends and Japanese national holidays are skipped, negative values reverse direction, and the operation is scoped to Japan's calendar. It doesn't discuss boundary edge cases, but the schema's min/max and year_end_break already frame those.

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 tight sentences: the operation and direction are front-loaded, then a single illustrative use case. Nothing is redundant with the schema and no sentence could be removed without loss.

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 low-complexity calendar computation with full annotation coverage and a fully documented schema, the description is nearly complete. The one gap is the return value — no output schema exists and the description never states that a resulting date is returned — which an agent must assume.

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%, with pattern, bounds, and the year_end_break default all documented in the schema itself. The description only restates the negative-direction behavior of days, which the schema already says ('negative goes back'), so it adds little beyond structured data — the baseline of 3 applies.

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?

States a concrete verb+resource: moving by N business days in Japan with weekends and national holidays skipped, and that negative values move backward. The scope is unambiguous, but it never names the sibling count_business_days, so an agent must infer whether it wants an offset or a difference between dates.

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?

The second sentence gives a clear usage context (due dates such as 'within 5 business days'), which is exactly the common case. It offers no explicit exclusions or pointers to alternatives such as count_business_days for counting between two dates, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.