Synthex Forge — x402 Paid Agent Services

Create Settlement Receipt

create_settlement_receipt

Destructive

Signed settlement-receipt verdict for a tx hash. use it rather than create_prepaid_capacity for settlement receipt, not prepaid capacity; an object with 43 fields including Content-Type, User-Agent. $0.01 USDC.

Input Schema

Name	Required	Description
`payee`	No	The payee this operation operates on. See the schema for its type and whether it is required.
`payer`	No	The payer this operation operates on. See the schema for its type and whether it is required.
`txHash`	No	The txHash this operation operates on. See the schema for its type and whether it is required.
`receipt`	No	The receipt to operate on.
`minConfirmations`	No	The minConfirmations this operation operates on. See the schema for its type and whether it is required.
`expectedAmountAtomic`	No	The expectedAmountAtomic this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`id`	No	The `id` field of the response.
`ok`	Yes	Whether the operation succeeded.
`to`	No	The `to` field of the response.
`rpc`	No	The `rpc` field of the response.
`from`	No	The `from` field of the response.
`note`	No	A note on how the answer was produced.
`block`	No	The `block` field of the response.
`error`	No	The machine-readable error code, when the operation failed.
`checks`	No	The individual checks that were run.
`detail`	Yes	Human-readable explanation of the verdict.
`method`	No	The `method` field of the response.
`params`	No	The `params` field of the response.
`reason`	No	Why the verdict was reached.
`sha256`	No	The `sha256` field of the response.
`txHash`	No	The `txHash` field of the response.
`jsonrpc`	No	The `jsonrpc` field of the response.
`receipt`	No	The `receipt` field of the response.
`settled`	No	The `settled` field of the response.
`verdict`	Yes	The decision this tool returned.
`findings`	No	The `findings` field of the response.
`logIndex`	No	The `logIndex` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`transfer`	No	The `transfer` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`assurance`	No	The `assurance` field of the response.
`User-Agent`	No	The `User-Agent` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`checksTotal`	No	The `checksTotal` field of the response.
`Content-Type`	No	The `Content-Type` field of the response.
`amountAtomic`	No	The `amountAtomic` field of the response.
`evidenceCore`	No	The `evidenceCore` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`confirmations`	No	The `confirmations` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`expectedPayee`	No	The `expectedPayee` field of the response.
`expectedPayer`	No	The `expectedPayer` field of the response.
`checksObserved`	No	The `checksObserved` field of the response.
`profileVersion`	No	Version of the answer profile.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`counterpartyAgrees`	No	The `counterpartyAgrees` field of the response.
`counterpartyReceipt`	No	The `counterpartyReceipt` field of the response.
`expectedAmountAtomic`	No	The `expectedAmountAtomic` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed45 schema fields changedOct 31, 2026

addedOutput schema / properties / Content-Type

Added value: +{
+  "description": "The `Content-Type` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / User-Agent

Added value: +{
+  "description": "The `User-Agent` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / algorithm

Added value: +{
+  "description": "The `algorithm` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / amountAtomic

Added value: +{
+  "description": "The `amountAtomic` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / assurance

Added value: +{
+  "description": "The `assurance` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / block

Added value: +{
+  "description": "The `block` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / canonicalSha256

Added value: +{
+  "description": "The `canonicalSha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / checks

Added value: +{
+  "description": "The individual checks that were run.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / checksObserved

Added value: +{
+  "description": "The `checksObserved` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / checksTotal

Added value: +{
+  "description": "The `checksTotal` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / confirmations

Added value: +{
+  "description": "The `confirmations` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / counterpartyAgrees

Added value: +{
+  "description": "The `counterpartyAgrees` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / counterpartyReceipt

Added value: +{
+  "description": "The `counterpartyReceipt` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / coverage_gaps

Added value: +{
+  "description": "The `coverage_gaps` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / ed25519Sig

Added value: +{
+  "description": "The `ed25519Sig` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / error

Added value: +{
+  "description": "The machine-readable error code, when the operation failed.",
+  "type": "string"
+}

addedOutput schema / properties / evidenceCore

Added value: +{
+  "description": "The `evidenceCore` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / expectedAmountAtomic

Added value: +{
+  "description": "The `expectedAmountAtomic` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / expectedPayee

Added value: +{
+  "description": "The `expectedPayee` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / expectedPayer

Added value: +{
+  "description": "The `expectedPayer` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / findings

Added value: +{
+  "description": "The `findings` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / from

Added value: +{
+  "description": "The `from` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / id

Added value: +{
+  "description": "The `id` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / jsonrpc

Added value: +{
+  "description": "The `jsonrpc` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / logIndex

Added value: +{
+  "description": "The `logIndex` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / method

Added value: +{
+  "description": "The `method` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

addedOutput schema / properties / ok

Added value: +{
+  "description": "Whether the operation succeeded.",
+  "type": "boolean"
+}

addedOutput schema / properties / params

Added value: +{
+  "description": "The `params` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / profileVersion

Added value: +{
+  "description": "Version of the answer profile.",
+  "type": "string"
+}

addedOutput schema / properties / publicKeyHex

Added value: +{
+  "description": "The `publicKeyHex` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

addedOutput schema / properties / receipt

Added value: +{
+  "description": "The `receipt` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / reproducibility

Added value: +{
+  "description": "The `reproducibility` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / rpc

Added value: +{
+  "description": "The `rpc` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / settled

Added value: +{
+  "description": "The `settled` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sha256

Added value: +{
+  "description": "The `sha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / signedBy

Added value: +{
+  "description": "The `signedBy` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / to

Added value: +{
+  "description": "The `to` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / transfer

Added value: +{
+  "description": "The `transfer` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / txHash

Added value: +{
+  "description": "The `txHash` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / required

Added value: +[
+  "detail",
+  "ok",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotent, so the safety profile is known. The description usefully adds the $0.01 USDC cost, which is real value. However it gives no warning about irreversibility or money movement, and the 'an object with 43 fields including Content-Type, User-Agent' line is meaningless here and slightly misleading against a 6-parameter schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences but they are run-on and poorly punctuated, and the '43 fields including Content-Type, User-Agent' clause is unparseable filler that does not earn its place. The core purpose is not front-loaded; the alternative-tool aside interrupts the first sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 needn't be explained, and annotations carry the destructive/irreversible profile. Still, for a payment-settling destructive tool the description omits what is actually created or signed and what the required inputs mean, and it substitutes a nonsensical '43 fields' claim, leaving an agent unable to confidently invoke it.

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 schema nominally documents all six parameters (though with boilerplate text). The description mentions only the tx hash and adds no semantics for payee, payer, receipt, minConfirmations or expectedAmountAtomic beyond what the schema already states, so baseline 3 is appropriate.

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

Purpose2/5

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

The description opens with a noun phrase ('Signed settlement-receipt verdict for a tx hash') rather than a clear verb+resource statement of what the tool creates, and it never confirms this is a creation/signing operation despite the tool name. The only differentiation is the confused aside referencing a sibling, and the '43 fields including Content-Type, User-Agent' fragment muddies rather than clarifies the actual action.

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?

It does name an alternative and give a selection rule: use this rather than `create_prepaid_capacity` for a settlement receipt. That is real when-to-use guidance, but it is the only exclusion, the phrasing is garbled ('for settlement receipt, not prepaid capacity'), and no preconditions (valid tx hash, required amount) are stated.

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

All Synthex Forge — x402 Paid Agent Services 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.