Mart402

Jp Dependent Threshold

jp_dependent_threshold

Idempotent

Income-wall analysis: tax, social insurance (1.06M/1.30M), spousal and student-dependent walls. $0.02/call. Deterministic, cites primary sources; errors and unverified rules are never billed. Choose this for 'how much can be earned before ...' questions: it locates the income walls (tax, social insurance, spousal, student dependent) for an annual income. It does not compute take-home pay (use jp_payroll_net).

Input Schema

Name	Required	Description
`year`	No	Calendar year
`as_of`	No	Calculation reference date YYYY-MM-DD (default today); selects the rules version
`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.
`annual_income_yen`	Yes	Expected annual income in yen

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

Changed3 schema fields changedSep 27, 2026
- changedInput schema / properties / annual_income_yen / description
```
Previous value: -"See the product's input spec in /catalog"New value: +"Expected annual income in yen"
```
- addedInput schema / properties / as_of / format
```
Added value: +"date"
```
- addedInput schema / properties / year / default
```
Added value: +2026
```
Changed3 schema fields changedSep 27, 2026
- addedInput schema / properties / annual_income_yen / description
```
Added value: +"See the product's input spec in /catalog"
```
- addedInput schema / properties / as_of / description
```
Added value: +"Calculation reference date YYYY-MM-DD (default today); selects the rules version"
```
- addedInput schema / properties / year / description
```
Added value: +"Calendar year"
```
AddedAug 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: per-call price ($0.02), billing policy (errors and unverified rules are never billed), determinism, and source citation behavior — none of which appear in the annotation block. It also implies the payment/auth path that explains why readOnlyHint is false, since the call is billed.

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 core purpose and pricing, and the routing sentence comes before the exclusion. The list of wall types is repeated twice (opening line and 'Choose this for' sentence), a minor redundancy that keeps it from a 5.

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?

An output schema exists, annotations cover idempotency and world-openness, and the schema fully documents params — the description supplies the remaining decision-relevant facts (cost, billing, determinism, alternative tool). Nothing an agent needs to select and call it correctly is missing.

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 year, as_of, x_payment, and annual_income_yen are already documented in the schema. The description only reinforces the annual-income input implicitly and adds no format or constraint detail beyond it. Baseline 3 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: it 'locates the income walls (tax, social insurance, spousal, student dependent) for an annual income.' It explicitly names the sibling it is not (jp_payroll_net) and what that sibling does instead, so an agent can distinguish it 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?

Gives an explicit trigger phrase ('how much can be earned before ...' questions) and an explicit exclusion with a named alternative ('does not compute take-home pay (use jp_payroll_net)'). Both the when and the when-not are stated.

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?