Skip to main content
Glama

Japan Calendar

Count Japanese business days

count_business_days
Read-onlyIdempotent

Count business days in Japan between two dates (both ends included unless include_start is false).

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "count_business_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesLast date, YYYY-MM-DD
fromYesFirst date, YYYY-MM-DD
include_startNoCount the first date too. Default true.
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

B3.4/5.0
Behavior3/5

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

Annotations already supply the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description only needs to add counting semantics. It does clarify endpoint inclusivity, but omits the behavior an agent most needs: whether Japanese public holidays are excluded, and whether the result is an integer count. The phrase "both ends included unless include_start is false" is also slightly imprecise, since include_start governs only the start date.

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?

A single front-loaded sentence with no filler, which is well suited to a simple computational tool. The parenthetical slightly blurs it by implying both endpoints are toggleable when only the start is.

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?

For a four-parameter computation tool with full schema coverage and read-only annotations, this is nearly sufficient. Still missing are the holiday rule (are Japanese national holidays excluded by default?) and the return shape, which has no output schema to cover it.

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%, including patterns, defaults, and the year_end_break rationale, so the schema carries parameter meaning. The description only restates the include_start default, adding little beyond it.

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 pairs a specific verb ("Count") with a specific resource and scope ("business days in Japan between two dates"), which is enough to separate it from add_business_days and check_date. It never names any sibling or explicitly rules one out, so it stops short of the top mark.

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 use case is implied clearly by "count business days between two dates," but there is no explicit when-to-use vs. when-not guidance and no pointer to add_business_days or list_holidays. An agent can infer the purpose but gets no routing help.

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.