Skip to main content
Glama

jimu (renamed to Tax Compass)

2つの日の間の営業日の数

jp_business_days_between
Read-onlyIdempotent

Count Japanese business days (営業日) between two dates, skipping Saturdays, Sundays and the official Japanese holidays from the Cabinet Office CSV. Calendar "bank" also skips Dec 31–Jan 3 (銀行の休日, 銀行法施行令 第5条). By default the start date is not counted and the end date is counted. It is meant for deadlines, payment terms (支払期日), delivery dates and "how many 営業日" questions. At most 1,100 days apart; dates outside the holiday data (currently up to 2027-12-31) return an error.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "jp_business_days_between"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes終わりの日(YYYY-MM-DD)
startYes始めの日(YYYY-MM-DD)
calendarNonational=土日と国民の祝日・休日を休み(既定)。bank=それに加えて 12/31〜1/3 も休み(銀行の休日)
count_endNo終わりの日を数えるか(既定 true)
count_startNo始めの日を数えるか(既定 false)

Output Schema

NameRequiredDescriptionDefault
notesYesこの答えに効いた決まり・前提(日本語)
resultYes
doc_urlYes人が読む説明のページ(式・出所・例)。利用者に次に読んでもらう先
sourcesYes
law_as_ofNo出所が書く法令の基準日(例:2026-04-01=令和8年4月1日現在法令等)
checked_onYesCyclix Agents が出所を最後に確かめた日
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only, idempotent annotations, the description discloses the holiday data source, the bank-calendar rule (Dec 31–Jan 3 under 銀行法施行令 第5条), the default counting convention, the 1,100-day limit, and the error behavior for dates outside holiday coverage through 2027-12-31.

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 definition is front-loaded with the core count operation and then layers calendar rules, defaults, use cases, and limits. Each sentence contributes operational information, and the total length is proportionate to the tool's rules and constraints.

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

Completeness5/5

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

For a deterministic read-only calculation tool with a full output schema and complete annotations, the description covers the holiday basis, counting convention, calendar variants, date-range limit, and error boundary. An agent has enough information to call it correctly without opening the schema.

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 all five parameters, including the calendar enum and count_start/count_end defaults, are already documented. The description reinforces the default counting convention and bank-calendar meaning, but adds little that is not already in the schema.

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 gives a specific verb and resource: count Japanese business days between two dates. It immediately qualifies the calculation with weekend, national holiday, and optional bank-holiday rules, so an agent can distinguish it from date-arithmetic siblings such as jp_add_business_days.

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 states concrete use cases: deadlines, payment terms (支払期日), delivery dates, and 'how many 営業日' questions. It does not explicitly name an alternative tool or exclusion condition, so it stops short of full when-to-use/when-not-to-use routing.

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.

Resources