Agent Decision & Evidence Tools (MCP + x402)

Recover a settled US Import Readiness result (free)

recover_us_import_readiness

Read-onlyIdempotent

FREE recovery when an x402 settlement succeeded but the signed response was lost. Returns only the already-settled result for the opaque job ID and recovery secret; it never performs a new lookup or creates a new charge.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes
`recovery_secret`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	No
`error`	No
`route`	No
`tariff`	No
`charged`	No	When present on an error, false means the failed result is uncharged.
`message`	No
`missing`	No
`pricing`	No
`privacy`	No
`product`	No
`recalls`	No
`receipt`	No
`settled`	No	When present on an error, false means no settlement occurred.
`unknown`	No
`accepted`	No
`contract`	No
`decision`	No
`validity`	No
`cost_view`	No
`retryable`	No
`error_code`	No
`extensions`	No
`forwarding`	No
`limitations`	No
`status_code`	No
`did_you_mean`	No
`entry_policy`	No
`next_actions`	No
`missing_checks`	No
`policy_version`	No
`partial_evidence`	No
`source_snapshots`	No
`input_fingerprint`	No
`regulatory_routing`	No
`ordinary_duty_component`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 6, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / job_id / pattern
```
Added value: +"^[A-Za-z0-9_-]{20,64}$"
```
removedInput schema / properties / job_id / title
```
Removed value: -"Job Id"
```
removedInput schema / properties / recovery_secret / title
```
Removed value: -"Recovery Secret"
```

removedInput schema / title

Removed value: -"recover_us_import_readiness_toolArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "contract",
+        "policy_version",
+        "decision",
+        "input_fingerprint",
+        "route",
+        "product",
+        "tariff",
+        "ordinary_duty_component",
+        "entry_policy",
+        "recalls",
+        "regulatory_routing",
+        "forwarding",
+        "cost_view",
+        "source_snapshots",
+        "next_actions",
+        "validity",
+        "limitations",
+        "pricing",
+        "privacy",
+        "receipt",
+        "extensions"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "description": "Structured result contract for recover_us_import_readiness. A success satisfies the documented success branch. A domain or tool error includes error and is not a successful settlement; unpaid x402 requirements are carried by the transport wrapper.",
+  "properties": {
+    "accepted": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "charged": {
+      "description": "When present on an error, false means the failed result is uncharged.",
+      "type": "boolean"
+    },
+    "contract": {
+      "type": "string"
+    },
+    "cost_view": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "decision": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "did_you_mean": {
+      "additionalProperties": true,
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "entry_policy": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "error": {
+      "oneOf": [
+        {
+          "type": "string"
+        },
+        {
+          "additionalProperties": true,
+          "properties": {
+            "code": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "message": {
+              "type": "string"
+            },
+            "param": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "message"
+          ],
+          "type": "object"
+        }
+      ]
+    },
+    "error_code": {
+      "type": "string"
+    },
+    "extensions": {
+      "additionalProperties": true,
+      "properties": {
+        "delivery-receipt": {
+          "additionalProperties": true,
+          "properties": {
+            "how_to_verify": {
+              "type": "string"
+            },
+            "issued_at": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "issuer": {
+              "type": "string"
+            },
+            "issuer_key": {
+              "type": "string"
+            },
+            "key_id": {
+              "type": "string"
+            },
+            "result_hash": {
+              "type": "string"
+            },
+            "service": {
+              "type": "string"
+            },
+            "signature": {
+              "type": "string"
+            },
+            "signed_message": {
+              "type": "string"
+            },
+            "standard": {
+              "const": "eucompliance-receipt/2",
+              "type": "string"
+            },
+            "subject": {
+              "type": "string"
+            },
+            "valid_until": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "verify_url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "standard",
+            "service",
+            "subject",
+            "result_hash",
+            "issued_at",
+            "valid_until",
+            "issuer",
+            "issuer_key",
+            "key_id",
+            "verify_url",
+            "how_to_verify",
+            "signature",
+            "signed_message"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "delivery-receipt"
+      ],
+      "type": "object"
+    },
+    "forwarding": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "input_fingerprint": {
+      "type": "string"
+    },
+    "limitations": {
+      "items": {},
+      "type": "array"
+    },
+    "message": {
+      "type": "string"
+    },
+    "missing": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "missing_checks": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_actions": {
+      "items": {},
+      "type": "array"
+    },
+    "ordinary_duty_component": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "partial_evidence": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "policy_version": {
+      "type": "string"
+    },
+    "pricing": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "privacy": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "product": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "recalls": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "receipt": {
+      "additionalProperties": true,
+      "properties": {
+        "how_to_verify": {
+          "type": "string"
+        },
+        "issued_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "issuer": {
+          "type": "string"
+        },
+        "issuer_key": {
+          "type": "string"
+        },
+        "key_id": {
+          "type": "string"
+        },
+        "result_hash": {
+          "type": "string"
+        },
+        "service": {
+          "type": "string"
+        },
+        "signature": {
+          "type": "string"
+        },
+        "signed_message": {
+          "type": "string"
+        },
+        "standard": {
+          "const": "eucompliance-receipt/2",
+          "type": "string"
+        },
+        "subject": {
+          "type": "string"
+        },
+        "valid_until": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "verify_url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "standard",
+        "service",
+        "subject",
+        "result_hash",
+        "issued_at",
+        "valid_until",
+        "issuer",
+        "issuer_key",
+        "key_id",
+        "verify_url",
+        "how_to_verify",
+        "signature",
+        "signed_message"
+      ],
+      "type": "object"
+    },
+    "regulatory_routing": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "route": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "settled": {
+      "description": "When present on an error, false means no settlement occurred.",
+      "type": "boolean"
+    },
+    "source_snapshots": {
+      "items": {},
+      "type": "array"
+    },
+    "status_code": {
+      "type": "integer"
+    },
+    "tariff": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "unknown": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "validity": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

AddedAug 22, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already communicate read-only, idempotent, non-destructive behavior, and the description adds context beyond those: it returns only the already-settled result, involves no new charge, and is free recovery rather than a fresh operation. It stops short of describing behavior on invalid secrets or missing recovery data, but the annotation coverage lowers the burden.

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 sentences with no filler. It front-loads the most decision-relevant facts: free recovery, the exact condition, what is returned, and what is explicitly not done.

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?

Given the tool's simple two-parameter shape, the read-only/idempotent annotations, and the presence of an output schema, the description covers the essential behavior and boundary conditions. An agent selecting among many siblings has enough context to invoke this tool correctly without additional detail.

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 description coverage is 0%, so the description must carry meaning for the parameters. It does so by identifying both parameters together as the 'opaque job ID and recovery secret' tied to the already-settled result. While it doesn't elaborate on the recovery_secret format or where these values come from, the phrasing gives enough role context for the two self-named parameters.

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 description states a specific verb ('recover') and a precise resource ('settled US Import Readiness result') and defines the exact trigger condition: an x402 settlement succeeded but the signed response was lost. It also explicitly distinguishes itself from a fresh lookup by saying it 'never performs a new lookup or creates a new charge.'

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?

The description clearly says when to use the tool: when an x402 settlement succeeded but the signed response was lost. It also provides a strong when-not signal by stating it never performs a new lookup or creates a new charge, which guides an agent away from using it for new readiness checks.

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

All Agent Decision & Evidence Tools (MCP + x402) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.