Mart402

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. Required by mode (default add): add -> from, days; between -> from, to; holidays -> year; deadline -> kind, base_date; wareki -> date.

Input Schema

Name	Required	Description	Default
`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`	No	Required by mode (default add): add -> from, days; between -> from, to; holidays -> year; deadline -> kind, base_date; wareki -> date.	add
`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)

Output Schema

Name	Required	Description
`body`	Yes	JSON body of the underlying call (see /samples/{product} for each product's shape)
`status`	Yes	HTTP status of the underlying call (200 result, 402 payment terms, 4xx input error)
`how_to_pay`	No
`receipt_id`	No	set on paid results; free re-fetch via get_receipt
`payment_required`	No	true when status is 402: body holds x402 payment terms, not a result. Pay and call again with x_payment

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

addedOutput schema / properties / how_to_pay
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / payment_required

Added value: +{
+  "description": "true when status is 402: body holds x402 payment terms, not a result. Pay and call again with x_payment",
+  "type": "boolean"
+}

addedOutput schema / properties / receipt_id

Added value: +{
+  "description": "set on paid results; free re-fetch via get_receipt",
+  "type": "string"
+}

Changed3 schema fields changedOct 19, 2026

addedInput schema / properties / mode / default
```
Added value: +"add"
```

changedInput schema / properties / mode / description

Previous value: -"One of: add, between, holidays, deadline, wareki"New value: +"Required by mode (default add): add -> from, days; between -> from, to; holidays -> year; deadline -> kind, base_date; wareki -> date."

changedInput schema / required

Previous value: -[
-  "mode"
-]New value: +[]

Changed1 schema field changedOct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "body": {
+      "description": "JSON body of the underlying call (see /samples/{product} for each product's shape)"
+    },
+    "status": {
+      "description": "HTTP status of the underlying call (200 result, 402 payment terms, 4xx input error)",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "status",
+    "body"
+  ],
+  "type": "object"
+}

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

A4.1/5.0

Behavior4/5

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

Beyond the annotations, the description discloses pricing ($0.003/call), determinism, primary-source citation, and a billing policy that errors and unverified rules are never charged. That is meaningful behavioral context for a paid endpoint. It does not explain the readOnlyHint=false flag or payment handshake flow, which the schema's x_payment field covers instead.

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?

Capabilities are front-loaded, followed by price, guarantees, and the mode contract — a sensible priority order. The mode mapping duplicates text already present in the schema's mode description, which is minor redundancy rather than noise.

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?

With an output schema present and full schema coverage, the description need not explain return values, and it covers all five modes and their required inputs. Only the optional x_payment flow and defaults like saturday_off are left entirely to the schema, which is acceptable.

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% across all 10 parameters, so the schema already documents each field including the mode enum. The description's mode-to-param mapping adds orientation but is largely a repeat of the mode parameter's own schema description, so baseline 3 is appropriate.

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 opening sentence names specific capabilities: Japanese holidays, business-day arithmetic, statutory filing deadlines with holiday shift, and wareki conversion. No sibling (jp_payroll_net, jp_consumption_tax, jp_social_insurance, etc.) covers holiday calendars or day arithmetic, so an agent can route here unambiguously.

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 mode-to-parameter contract ('add -> from, days; between -> from, to; holidays -> year; deadline -> kind, base_date; wareki -> date') tells the agent exactly how to configure a call for each use case. It gives clear context but no explicit when-not or alternative-tool guidance, since no sibling offers overlapping functionality.

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

All Mart402 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?