Skip to main content
Glama

AINumbers Fintech Intelligence Suite

x402 V2 Batch-Settlement Reconciler

reconcile_x402_batch_settlement
Read-onlyIdempotent

x402 V2 Batch-Settlement Reconciler: OpenChainGraph compute node (settlement_mandate). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic or anonymised inputs only. Exports an AP2 artifact with execution_hash for chain provenance. Consumes upstream artifacts from: art-03-x402-settlement-modeler, art-60-agent-economy-runtime-fit-diagnostic. Output feeds: art-62-ap2-payment-receipt-verifier, cry-04-merkle-batch-verifier, cry-05-agent-action-audit-trail-aggregator. Open at: https://ainumbers.co/chaingraph/art-61-x402-batch-settlement-reconciler.html FV-status (published/proven/still-trusted for this spec): /fv-status/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Reconciles an x402 V2 batch settlement (off-chain payment vouchers vs onchain batch total), verifying recon verdict, per-voucher amounts, settlement-risk window (unredeemed voucher exposure), and computing an educational Merkle root over the voucher set. Outputs: batch_delta_minor_units, batch_id, escrow_address, merkle_root_preimage, note, recon_verdict, redeemed_count, redeemed_total, settlement_asset, settlement_risk_window, status_asof, unredeemed_value, voucher_count, voucher_findings, within_tolerance. Output schema: call describe_tool("reconcile_x402_batch_settlement").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reconcile_x402_batch_settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
computeNoCompute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always return browser delegation URL. gpu:true nodes always delegate.
parent_hashesNoexecution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
parent_tool_idsNotool_id values matching parent_hashes, in the same order.
policy_parametersNoInput parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "server". Unknown keys are refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changed
    • changedInput schema / properties / policy_parameters / description
      Previous value: -"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". See the tool's manifest for field names."New value: +"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "batch": {},
      +  "finality_threshold": {},
      +  "tolerance_minor_units": {},
      +  "vouchers": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "batch_delta_minor_units": {
      -      "type": "integer"
      -    },
      -    "batch_id": {
      -      "type": "string"
      -    },
      -    "escrow_address": {
      -      "type": "string"
      -    },
      -    "merkle_root_preimage": {
      -      "type": "string"
      -    },
      -    "note": {
      -      "type": "string"
      -    },
      -    "recon_verdict": {
      -      "type": "string"
      -    },
      -    "redeemed_count": {
      -      "type": "integer"
      -    },
      -    "redeemed_total": {
      -      "type": "integer"
      -    },
      -    "settlement_asset": {
      -      "type": "string"
      -    },
      -    "settlement_risk_window": {
      -      "type": "integer"
      -    },
      -    "status_asof": {
      -      "type": "string"
      -    },
      -    "unredeemed_value": {
      -      "type": "integer"
      -    },
      -    "voucher_count": {
      -      "type": "integer"
      -    },
      -    "voucher_findings": {
      -      "type": "array"
      -    },
      -    "within_tolerance": {
      -      "type": "boolean"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "batch_delta_minor_units": {
      +      "type": "integer"
      +    },
      +    "batch_id": {
      +      "type": "string"
      +    },
      +    "escrow_address": {
      +      "type": "string"
      +    },
      +    "merkle_root_preimage": {
      +      "type": "string"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "recon_verdict": {
      +      "type": "string"
      +    },
      +    "redeemed_count": {
      +      "type": "integer"
      +    },
      +    "redeemed_total": {
      +      "type": "integer"
      +    },
      +    "settlement_asset": {
      +      "type": "string"
      +    },
      +    "settlement_risk_window": {
      +      "type": "integer"
      +    },
      +    "status_asof": {
      +      "type": "string"
      +    },
      +    "unredeemed_value": {
      +      "type": "integer"
      +    },
      +    "voucher_count": {
      +      "type": "integer"
      +    },
      +    "voucher_findings": {
      +      "type": "array"
      +    },
      +    "within_tolerance": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, non-destructive, closed-world), and the description still adds genuinely new behavioral facts: server-side vs browser-delegation execution paths for gpu:true nodes, transient processing with no storage/logging/retention, the obligation to use synthetic inputs, AP2 artifact export with execution_hash, and an FV-status receipt that verifies offline. The only weak spot is that 'Exports an AP2 artifact' is never reconciled with the read-only hint, though as a compute node returning an artifact in the response this reads as consistent rather than contradictory.

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?

The most important sentence — what the tool actually reconciles — appears last, after compute-mode plumbing, a privacy note, an artifact chain, a raw URL, and a 64-character FV-status hash. Roughly half the text is ChainGraph platform boilerplate (compute binding, FV-status snapshot, 'Open at' link) that does not help an agent decide or invoke. The content is not padded per se, but the ordering actively works against front-loading.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does the right thing by enumerating return fields (recon_verdict, batch_delta_minor_units, settlement_risk_window, within_tolerance, etc.), so return-shape expectations are covered. However, for a tool with a nested object parameter and four policy inputs, the inner input semantics are left entirely unstated, and the tolerance/finality semantics that determine recon_verdict are never explained. Adequate but with a real gap on the decision inputs.

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 already documents compute, parent_hashes, parent_tool_ids, and policy_parameters, and the description mostly restates the compute-mode semantics already present in the schema. The one place the description could add value it does not is the nested policy_parameters object, whose inner keys (batch, vouchers, finality_threshold, tolerance_minor_units) are undocumented in both schema and description. Baseline 3 is appropriate when the schema carries the weight.

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 'Summary:' line states a specific verb and resource: reconcile an x402 V2 batch settlement of off-chain vouchers against the onchain batch total, and names the concrete sub-verifications (recon verdict, per-voucher amounts, settlement-risk window, Merkle root). It is distinguishable from neighbours like model_x402_settlement or simulate_x402_flow via the upstream/downstream artifact lists, but the differentiation is implicit in the graph chain rather than stated outright. The actual purpose is also buried at the very end behind infrastructure boilerplate.

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?

Usage context is only implied through the artifact wiring ('Consumes upstream artifacts from art-03-x402-settlement-modeler... Output feeds art-62...'), which tells an agent where this fits in a chain but not explicitly when to pick it over a sibling reconciler or verifier. The 'Use synthetic or anonymised inputs only' line is a real constraint but is a data-handling rule, not a use-vs-alternative rule. No exclusions or prerequisites are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.