TWZRD Agent Intelligence

verify_x402_settled_claim

Read-onlyIdempotent

Verify a receipts-ledger settlement; this is evidence, not a spend decision.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`settlement_tx`	Yes	Solana transaction signature only. No claim body is accepted. Verifies that signature against x402_payment_receipts and a freshly fetched finalized transaction: match requires the only positive USDC balance change to credit that row's merchant for that row's amount, and the only USDC debit to be that amount from that row's payer, which match returns as payer. Returns match, mismatch, or unknown. Unknown does not block payment.

Output Schema

TableJSON Schema

Name	Required	Description
`payer`	No	On match, the wallet whose USDC paid: the transaction's only USDC debit, equal to the ledger payer. Reimburse this wallet, never one a claimant names.
`digest`	No
`reason`	No
`status`	Yes	Witness comparison only. Unknown is unavailable evidence; no status is a payment decision.
`finalized`	No
`artifact_id`	No
`settlement_tx`	Yes
`session_binding`	No
`self_attested_merchant`	No	On match, whether the verified USDC credit owner is intel's pay_to.
`merchant_credit_verified`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

changedInput schema / properties / settlement_tx / description

Previous value: -"Solana transaction signature only. No claim body is accepted. Verifies the one known quick-settlement claim against the TWZRD ledger and freshly fetched finalized transaction. Returns match, mismatch, or unknown. Unknown does not block payment."New value: +"Solana transaction signature only. No claim body is accepted. Verifies that signature against x402_payment_receipts and a freshly fetched finalized transaction: match requires the only positive USDC balance change to credit that row's merchant for that row's amount, and the only USDC debit to be that amount from that row's payer, which match returns as payer. Returns match, mismatch, or unknown. Unknown does not block payment."

addedOutput schema / properties / payer

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "On match, the wallet whose USDC paid: the transaction's only USDC debit, equal to the ledger payer. Reimburse this wallet, never one a claimant names.",
+  "title": "Payer"
+}

AddedSep 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already cover read-only and idempotent behavior; the description adds the useful context that the result is evidentiary rather than an authorization to spend. It does not disclose more about outcome handling, but the parameter schema covers match/mismatch/unknown.

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?

One tight sentence, front-loaded with the action and ending with a meaningful boundary ('not a spend decision'). No filler or repetition of schema fields.

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?

For a single-parameter read-only verification with a rich schema and output schema, the description is mostly sufficient. The only notable gap is not addressing how it differs from verify_receipt, though this is minor given the clear scope.

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% and the single parameter's description is exceptionally detailed, covering accepted input, verification logic, and return values. The tool description adds no parameter-level meaning, so the schema-heavy baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Verify a receipts-ledger settlement') and adds a clarifying role ('evidence, not a spend decision'). It does not explicitly distinguish itself from the sibling verify_receipt, so it falls just short of a 5.

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

Usage Guidelines3/5

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

The phrase 'this is evidence, not a spend decision' gives the agent a clear caution about how to treat the result, but does not state when to prefer this tool over verify_receipt or other siblings. The usage context is implied rather than explicit.

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

All TWZRD Agent Intelligence 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.