Mart402

Jp Payroll Suite

jp_payroll_suite

Idempotent

Japan payroll suite: net salary + social insurance + income walls (+bonus) in one call. Flat $0.05. Choose this when you want take-home pay, social insurance and the income walls (and the bonus, if given) together from one annual figure in one call; if you only need the take-home amount, jp_payroll_net is cheaper.

Input Schema

Name	Required	Description
`age`	No	Age in years (selects care-insurance and other age-gated rules)
`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.
`dependents`	No	Dependents object (see /catalog input spec)
`prefecture`	Yes	Prefecture (romaji or Japanese), e.g. 'Tokyo'
`annual_bonus_yen`	No	Annual bonus total in yen
`annual_gross_yen`	Yes	Annual gross salary in yen
`previous_month_after_si_yen`	No	Previous month's pay after social insurance (withholding table lookup)

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

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

Changed6 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 / annual_bonus_yen / description
```
Added value: +"Annual bonus total in yen"
```
- addedInput schema / properties / annual_gross_yen / description
```
Added value: +"Annual gross salary in yen"
```
- addedInput schema / properties / dependents / description
```
Added value: +"Dependents object (see /catalog input spec)"
```
- addedInput schema / properties / prefecture / description
```
Added value: +"Prefecture (romaji or Japanese), e.g. 'Tokyo'"
```
- addedInput schema / properties / previous_month_after_si_yen / description
```
Added value: +"Previous month's pay after social insurance (withholding table lookup)"
```
AddedAug 19, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the one genuinely new behavioral fact, the flat $0.05 charge, but says nothing about how the x402 payment flow behaves or what happens when required inputs are missing. Useful addition, not rich context.

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 composite scope and cost, then the routing rule. Slightly wasteful: 'in one call' is repeated twice and 'Flat $0.05' could be merged into the selection sentence, but the whole thing is short and every part is functional.

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?

An output schema exists, so return values need no explanation, and the annotations cover idempotency and safety. What remains thin is the payment path: the x_payment parameter's charge-avoidance behavior is only in the schema, not reinforced against the advertised $0.05. Adequate for a 7-parameter composite calculator.

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 the baseline is 3. The description only restates that the calculation derives from 'one annual figure' and 'the bonus, if given'; it adds no meaning about prefecture, age, dependents or previous_month_after_si_yen beyond what the schema documents.

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 composite resource: net salary, social insurance and income walls computed from one annual gross figure, optionally with bonus. It explicitly names the sibling it is not (jp_payroll_net) and the difference between them, so an agent can route without opening either 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 when-to-use ('when you want take-home pay, social insurance and the income walls... in one call') and when-not ('if you only need the take-home amount, jp_payroll_net is cheaper'), with a cost-based selection criterion. Nothing is left to inference.

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?