RunOnProof — Payment Decision and Agent ID

release_payment_to_supplier

Read-onlyIdempotent

Paid RunOnProof Payment Decision: one US FEDERAL_ONLY release-payment decision for 0.79 USDC on Base, with signed BuyerPaymentMandate, signed Proof Capsule and deterministic replay. RunOnProof does not execute supplier payment.

Input Schema

TableJSON Schema

Name	Required	Description
`buyer`	Yes
`payee`	Yes
`amount`	Yes
`intent`	Yes
`invoice`	Yes
`coverage`	Yes
`currency`	Yes
`supplier`	Yes
`disclosure`	Yes
`correlation`	Yes
`risk_policy`	Yes
`jurisdiction`	Yes
`buyer_mandate`	Yes	Signed BuyerPaymentMandate bound to this request digest, buyer, agent, supplier, payee, limits and validity window.
`schema_version`	Yes
`idempotency_key`	Yes
`economic_purpose`	Yes
`requesting_agent`	Yes
`decision_fee_payer`	No	Decision fee wallet authorized by the signed request and buyer mandate; required for commercial x402 purchases.
`evidence_references`	Yes
`payment_destination`	Yes
`coverage_requirements`	Yes
`freshness_requirements`	Yes
`exposure_valuation_basis`	Yes
`payment_instruction_digest`	Yes
`payment_exposure_usdc_equivalent_atomic`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`policy`	Yes
`replay`	Yes
`billing`	Yes
`product`	Yes
`coverage`	Yes
`decision`	Yes
`delivery`	Yes
`freshness`	Yes
`conditions`	Yes
`request_id`	Yes
`decision_id`	Yes
`remediation`	Yes
`uncertainty`	Yes
`valid_as_of`	Yes
`valid_until`	Yes
`reason_codes`	Yes
`risk_signals`	Yes
`checks_waived`	Yes
`decision_cost`	Yes
`economic_risk`	Yes
`proof_capsule`	Yes
`machine_action`	Yes
`request_digest`	Yes
`schema_version`	Yes
`checks_executed`	Yes
`evidence_bundle`	Yes
`product_version`	Yes
`payment_executed`	Yes
`decision_request_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 7, 2026

removedInput schema / properties / payee / $ref

Removed value: -"#/components/schemas/DecisionGatePayee"

addedInput schema / properties / payee / additionalProperties
```
Added value: +false
```

addedInput schema / properties / payee / properties

Added value: +{
+  "fingerprint": {
+    "pattern": "^sha256:[0-9a-f]{64}$",
+    "type": "string"
+  },
+  "provider_namespace": {
+    "type": "string"
+  },
+  "type": {
+    "enum": [
+      "X402_PAYTO",
+      "WALLET",
+      "MERCHANT_RESOURCE",
+      "PAYOUT_DESTINATION_TOKEN",
+      "PROVIDER_ACCOUNT_TOKEN"
+    ]
+  },
+  "value": {
+    "type": "string"
+  }
+}

addedInput schema / properties / payee / required

Added value: +[
+  "type",
+  "value",
+  "fingerprint"
+]

addedInput schema / properties / payee / type
```
Added value: +"object"
```
removedInput schema / properties / payment_destination / $ref
```
Removed value: -"#/components/schemas/DecisionGatePayee"
```
addedInput schema / properties / payment_destination / additionalProperties
```
Added value: +false
```

addedInput schema / properties / payment_destination / properties

Added value: +{
+  "fingerprint": {
+    "pattern": "^sha256:[0-9a-f]{64}$",
+    "type": "string"
+  },
+  "provider_namespace": {
+    "type": "string"
+  },
+  "type": {
+    "enum": [
+      "X402_PAYTO",
+      "WALLET",
+      "MERCHANT_RESOURCE",
+      "PAYOUT_DESTINATION_TOKEN",
+      "PROVIDER_ACCOUNT_TOKEN"
+    ]
+  },
+  "value": {
+    "type": "string"
+  }
+}

addedInput schema / properties / payment_destination / required
```
Added value: +[
+  "type",
+  "value",
+  "fingerprint"
+]
```
addedInput schema / properties / payment_destination / type
```
Added value: +"object"
```

Changed1 schema field changedSep 6, 2026

addedInput schema / properties / decision_fee_payer

Added value: +{
+  "description": "Decision fee wallet authorized by the signed request and buyer mandate; required for commercial x402 purchases.",
+  "pattern": "^0x[0-9a-fA-F]{40}$",
+  "type": "string"
+}

Changed5 schema fields changedSep 4, 2026

addedInput schema / properties / buyer_mandate / properties / payload / additionalProperties
```
Added value: +false
```

addedInput schema / properties / buyer_mandate / properties / payload / properties

Added value: +{
+  "buyer_organization": {
+    "maxLength": 160,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]*$",
+    "type": "string"
+  },
+  "buyer_organization_digest": {
+    "pattern": "^sha256:[0-9a-f]{64}$",
+    "type": "string"
+  },
+  "currency": {
+    "pattern": "^[A-Z]{3}$",
+    "type": "string"
+  },
+  "issuer": {
+    "maxLength": 160,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]*$",
+    "type": "string"
+  },
+  "key_id": {
+    "maxLength": 160,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]*$",
+    "type": "string"
+  },
+  "mandate_id": {
+    "maxLength": 160,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]*$",
+    "type": "string"
+  },
+  "mandate_version": {
+    "pattern": "^\\d+\\.\\d+\\.\\d+$",
+    "type": "string"
+  },
+  "max_decision_fee_atomic": {
+    "pattern": "^\\d+$",
+    "type": "string"
+  },
+  "max_payment_amount": {
+    "pattern": "^(0|[1-9][0-9]{0,17})(\\.[0-9]{1,6})?$",
+    "type": "string"
+  },
+  "nonce": {
+    "maxLength": 96,
+    "minLength": 16,
+    "pattern": "^[A-Za-z0-9_-]+$",
+    "type": "string"
+  },
+  "payee_fingerprint": {
+    "pattern": "^sha256:[0-9a-f]{64}$",
+    "type": "string"
+  },
+  "permitted_intent": {
+    "const": "RELEASE_PAYMENT_TO_SUPPLIER"
+  },
+  "request_digest": {
+    "pattern": "^sha256:[0-9a-f]{64}$",
+    "type": "string"
+  },
+  "revocation_reference": {
+    "maxLength": 512,
+    "minLength": 1,
+    "type": "string"
+  },
+  "schema_version": {
+    "const": "1.0.0"
+  },
+  "subject_agent_id": {
+    "maxLength": 160,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]*$",
+    "type": "string"
+  },
+  "supplier_entity_id": {
+    "maxLength": 160,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]*$",
+    "type": "string"
+  },
+  "valid_from": {
+    "format": "date-time",
+    "type": "string"
+  },
+  "valid_until": {
+    "format": "date-time",
+    "type": "string"
+  }
+}

addedInput schema / properties / buyer_mandate / properties / payload / required

Added value: +[
+  "schema_version",
+  "mandate_id",
+  "mandate_version",
+  "issuer",
+  "subject_agent_id",
+  "buyer_organization",
+  "buyer_organization_digest",
+  "permitted_intent",
+  "request_digest",
+  "supplier_entity_id",
+  "payee_fingerprint",
+  "max_payment_amount",
+  "currency",
+  "max_decision_fee_atomic",
+  "valid_from",
+  "valid_until",
+  "nonce",
+  "key_id",
+  "revocation_reference"
+]

addedInput schema / properties / buyer_mandate / properties / signature / additionalProperties
```
Added value: +false
```

addedInput schema / properties / buyer_mandate / properties / signature / properties

Added value: +{
+  "algorithm": {
+    "const": "Ed25519"
+  },
+  "canonicalization": {
+    "const": "ROP-C14N-JSON-1"
+  },
+  "issuer": {
+    "maxLength": 160,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]*$",
+    "type": "string"
+  },
+  "key_id": {
+    "maxLength": 160,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]*$",
+    "type": "string"
+  },
+  "value": {
+    "pattern": "^[A-Za-z0-9_-]{86}$",
+    "type": "string"
+  }
+}

AddedSep 2, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds meaningful context on top: the decision is 'Paid', replay is deterministic, and the tool does not execute supplier payment. These are behavioral details not inferable from annotations, and there is no contradiction.

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

Conciseness3/5

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

The text is compact and front-loads the central purpose, but the very specific '0.79 USDC' and the dense stack of qualifiers add noise. A more general statement of the tool's capability would be clearer without losing conciseness.

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?

For a tool with 25 parameters, 24 required, nested objects, and almost no schema descriptions, the definition provides only high-level scope. It mentions US-only, FEDERAL_ONLY, deterministic replay, and non-execution, but omits fee mechanics, idempotency expectations, and any guidance on the large required payload. The output schema helps with return values but not with invocation requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 8%, so the description should compensate by explaining key parameters, but it does not. The only hint is 'signed BuyerPaymentMandate, signed Proof Capsule', which maps loosely to buyer_mandate and evidence references, while critical fields like idempotency_key, jurisdiction, coverage, and payout amounts go unexplained.

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 identifies a specific resource: a paid RunOnProof release-payment decision, limited to a US FEDERAL_ONLY context, and explicitly distinguishes itself from actual supplier payment execution. However, the hardcoded '0.79 USDC on Base' makes it read like a single transaction instance rather than a general tool, and no sibling tool is named for differentiation.

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 description implies the situation: use this when a release-payment decision is needed, and the closing statement 'RunOnProof does not execute supplier payment' provides a when-not boundary. But it never states explicit conditions for choosing this tool over siblings like preflight or quote, nor does it describe any alternative.

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

All RunOnProof — Payment Decision and Agent ID 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?