extract

Jp Business Days

jp_business_days

Idempotent

Japanese holidays, business-day arithmetic, statutory filing deadlines with holiday shift, wareki conversion. $0.003/call. Deterministic, cites primary sources; errors and unverified rules are never billed.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	End date YYYY-MM-DD
`date`	No	Date YYYY-MM-DD
`days`	No	Number of business days to add
`from`	No	Start date YYYY-MM-DD
`kind`	No	One of: withholding_tax_monthly, social_insurance_monthly, corporate_tax, consumption_tax_corporate, income_tax_final, consumption_tax_individual, depreciable_assets, legal_records. Statutory deadline kind (see enum)
`mode`	Yes	One of: add, between, holidays, deadline, wareki
`year`	No	Calendar year
`base_date`	No	Base date YYYY-MM-DD for deadline calculation
`x_payment`	No	Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged.
`saturday_off`	No	Treat Saturdays as non-business days (default true)

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 27, 2026

changedInput schema / properties / base_date / description

Previous value: -"See the product's input spec in /catalog"New value: +"Base date YYYY-MM-DD for deadline calculation"

addedInput schema / properties / base_date / format
```
Added value: +"date"
```

changedInput schema / properties / date / description

Previous value: -"See the product's input spec in /catalog"New value: +"Date YYYY-MM-DD"

addedInput schema / properties / date / format
```
Added value: +"date"
```
addedInput schema / properties / from / format
```
Added value: +"date"
```

changedInput schema / properties / kind / description

Previous value: -"See the product's input spec in /catalog"New value: +"One of: withholding_tax_monthly, social_insurance_monthly, corporate_tax, consumption_tax_corporate, income_tax_final, consumption_tax_individual, depreciable_assets, legal_records. Statutory deadline kind (see enum)"

addedInput schema / properties / kind / enum

Added value: +[
+  "withholding_tax_monthly",
+  "social_insurance_monthly",
+  "corporate_tax",
+  "consumption_tax_corporate",
+  "income_tax_final",
+  "consumption_tax_individual",
+  "depreciable_assets",
+  "legal_records"
+]

changedInput schema / properties / mode / description

Previous value: -"Extraction mode: auto (fast with rendered fallback), fast, heavy"New value: +"One of: add, between, holidays, deadline, wareki"

addedInput schema / properties / mode / enum

Added value: +[
+  "add",
+  "between",
+  "holidays",
+  "deadline",
+  "wareki"
+]

addedInput schema / properties / saturday_off / default
```
Added value: +true
```

changedInput schema / properties / saturday_off / description

Previous value: -"See the product's input spec in /catalog"New value: +"Treat Saturdays as non-business days (default true)"

addedInput schema / properties / to / format
```
Added value: +"date"
```

Changed9 schema fields changedSep 27, 2026
- addedInput schema / properties / base_date / description
```
Added value: +"See the product's input spec in /catalog"
```
- addedInput schema / properties / date / description
```
Added value: +"See the product's input spec in /catalog"
```
- addedInput schema / properties / days / description
```
Added value: +"Number of business days to add"
```
- addedInput schema / properties / from / description
```
Added value: +"Start date YYYY-MM-DD"
```
- addedInput schema / properties / kind / description
```
Added value: +"See the product's input spec in /catalog"
```
- addedInput schema / properties / mode / description
```
Added value: +"Extraction mode: auto (fast with rendered fallback), fast, heavy"
```
- addedInput schema / properties / saturday_off / description
```
Added value: +"See the product's input spec in /catalog"
```
- addedInput schema / properties / to / description
```
Added value: +"End date YYYY-MM-DD"
```
- addedInput schema / properties / year / description
```
Added value: +"Calendar year"
```
AddedAug 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations provide idempotentHint:true, readOnlyHint:false, and destructiveHint:false, but the description adds meaningful independent context: deterministic behavior, citation of primary sources, and a guarantee that errors/unverified rules are never billed. It also adds pricing information not present in annotations. No contradiction exists.

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 is two tight sentences. The first front-loads every core capability; the second adds pricing and trust signals. Every sentence earns its place, and there is no filler or repetition.

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 5-mode, 10-parameter tool with no output schema, the description gives a strong high-level summary but does not clarify which parameters apply to which mode or what return shape to expect. The schema documents individual parameters, but an agent still has to infer combinations like mode=add with date+days or mode=deadline with kind+base_date. This is a moderate completeness gap.

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 input schema covers all 10 parameters with 100% description coverage, so the description does not need to restate parameter meanings. It adds high-level mode categories like 'deadline' and 'wareki', but no additional syntax or cross-parameter guidance beyond the schema. Baseline 3 is appropriate.

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 names five concrete capabilities: Japanese holidays, business-day arithmetic, statutory filing deadlines with holiday shift, and wareki conversion. It clearly identifies the resource and domain, though it lacks a single imperative verb like 'calculate' or 'return'. The listed capabilities distinguish it from the many jp_* sibling tools.

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 implies usage context by listing the main operations, but it never states when not to use the tool or which sibling might be a better alternative. Given the large sibling set of Japanese tax/payroll tools, explicit routing would be valuable. The context is clear, but exclusions are absent.

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

All extract tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?