Mart402

Jp Payslip Audit

jp_payslip_audit

Idempotent

Audit a Japanese payslip: recompute statutory premiums and withholding tax from official tables and diff against the actual amounts, with per-item verdicts (match/explainable/mismatch). $0.02/call. Deterministic, cites primary sources; errors and unverified rules are never billed. Choose this when you HAVE an actual payslip and want each deduction checked against the official tables (match/explainable/mismatch); to compute expected amounts from a salary alone use jp_payroll_net or jp_social_insurance.

Input Schema

Name	Required	Description
`age`	No	Age in years (selects care-insurance and other age-gated rules)
`as_of`	No	Calculation reference date YYYY-MM-DD (default today); selects the rules version
`payslip`	Yes	Payslip fields to audit - see /catalog input spec
`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.
`prefecture`	Yes	Prefecture (romaji or Japanese), e.g. 'Tokyo'
`standard_monthly_yen`	No	Standard monthly remuneration if known (else estimated from salary)

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"
+}

Changed2 schema fields changedOct 19, 2026
- addedInput schema / properties / payslip / properties
```
Added value: +{
+  "monthly_gross_yen": {
+    "type": "integer"
+  }
+}
```
- addedInput schema / properties / payslip / required
```
Added value: +[
+  "monthly_gross_yen"
+]
```

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"
+}

Changed3 schema fields changedSep 27, 2026
- addedInput schema / properties / age / default
```
Added value: +30
```
- addedInput schema / properties / as_of / format
```
Added value: +"date"
```
- changedInput schema / properties / standard_monthly_yen / description
```
Previous value: -"See the product's input spec in /catalog"New value: +"Standard monthly remuneration if known (else estimated from salary)"
```

Changed5 schema fields changedSep 27, 2026

addedInput schema / properties / age / description

Added value: +"Age in years (selects care-insurance and other age-gated rules)"

addedInput schema / properties / as_of / description

Added value: +"Calculation reference date YYYY-MM-DD (default today); selects the rules version"

addedInput schema / properties / payslip / description

Added value: +"Payslip fields to audit - see /catalog input spec"

addedInput schema / properties / prefecture / description

Added value: +"Prefecture (romaji or Japanese), e.g. 'Tokyo'"

addedInput schema / properties / standard_monthly_yen / description
```
Added value: +"See the product's input spec in /catalog"
```

AddedAug 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well past the annotations by disclosing cost ($0.02/call), billing exclusions (errors and unverified rules never billed), determinism, and source citation behavior. The x_payment parameter note completes the payment flow: omitting it returns accepts[]/docs without a charge, which resolves the main operational risk for a paid tool.

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?

Front-loaded with the action and result, then pricing, then the routing rule; no sentence is filler. It is dense – three distinct concerns packed into one block – but each earns its place for a paid, deterministic audit tool.

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?

With an output schema present, return values need not be explained, and the description still summarizes the verdict taxonomy. Payment mechanics, billing guarantees, determinism, and sibling routing are all covered, so an agent has everything needed to decide and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns a 4 by tying parameters to behavior: 'as_of' selects the rules version and 'age' gates care-insurance and age-dependent rules, which is genuinely useful model context. It does not, however, explain the nested 'payslip' payload beyond pointing to '/catalog input spec', leaving the required payload shape off-tool.

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 ('Audit a Japanese payslip') plus the method: recompute statutory premiums and withholding tax from official tables and diff against actual amounts. The output artifact (per-item match/explainable/mismatch verdicts) is named, so an agent knows exactly what it gets back, and the tool is distinguishable from the calculation siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit selection rule: 'Choose this when you HAVE an actual payslip'. It also names the contrasting condition and the specific alternatives ('to compute expected amounts from a salary alone use jp_payroll_net or jp_social_insurance'), so the boundary against the two closest siblings is unambiguous.

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?