Skip to main content
Glama

jimu (renamed to Tax Compass)

N 営業日後・前の日

jp_add_business_days
Read-onlyIdempotent

Return the date N Japanese business days after (or before, if N is negative) a start date; the start date itself is never counted. Same calendars as jp_business_days_between (national holidays from the Cabinet Office CSV; "bank" also skips Dec 31–Jan 3). Use it for "5営業日後" style deadlines. N must be a non-zero integer from -400 to 400.

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>",
      "days": "<days>"
    },
    "name": "jp_add_business_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes何営業日後か。負の数なら前。0 は不可
startYes始めの日(YYYY-MM-DD)。この日は数えない
calendarNonational=土日と国民の祝日・休日を休み(既定)。bank=それに加えて 12/31〜1/3 も休み(銀行の休日)

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.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered; the description adds real behavior on top: the start date is never counted, negative N moves backwards, and the calendar choice affects which days are skipped. The domain constraints (non-zero N, -400..400) are also restated, though return shape is left to the output schema.

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, front-loaded with the operation and its direction semantics, followed by calendar provenance and the intended use case. No filler or repetition beyond a brief restatement of the N bounds.

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 three-parameter date calculator with full annotations, a 100%-covered schema and an output schema, nothing an agent needs to invoke it correctly is missing. Calendar provenance (Cabinet Office CSV) and the exclusion rule are the right level of detail.

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 days, start and calendar are already documented including the 'this day is not counted' note and the bank-holiday extension. The description largely mirrors that content rather than adding syntax or edge-case meaning beyond it, so the baseline applies.

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?

States a specific verb and resource ('Return the date N Japanese business days after/before a start date') and pins down the exclusive counting rule that separates it from the sibling counting tool jp_business_days_between. An agent can route to it 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 Guidelines4/5

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

Gives concrete usage context ('Use it for "5営業日後" style deadlines') and points at jp_business_days_between for the shared calendar definition, which implicitly frames the alternative. It stops short of an explicit when-not-to-use rule (e.g. use the between tool when you need elapsed business days rather than a computed date).

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