Skip to main content
Glama

AINumbers Fintech Intelligence Suite

by co.ainumbers
OverviewDiscussionsAdmin

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/8498d0819c941fdb731f9e10f5d93ee929026919cb111a42149821b48b5ac180.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Output schema: call describe_tool("reconcile_x402_batch_settlement").

Input Schema

TableJSON 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". See the tool's manifest for field names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. 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"
+}
  3. Added

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes further with genuinely useful context: deterministic execution, the auto/server/browser delegation rules including 'gpu:true nodes always delegate', and explicit transient-processing guarantees ('not stored, logged, or retained') with a synthetic-inputs-only caveat. It does not contradict the annotations.

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 front-loaded name/verb is fine, but the payload is bloated with low-value tokens: a raw URL, a 64-character FV-status hash, and a 'a snapshot, not a subscription' aside that no agent needs to select or call the tool. The description is a run-on sentence chain rather than an ordered set of call-relevant facts.

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?

Provenance, chaining, and data-handling are well covered, and there is no output schema so return values needn't be explained. But with policy_parameters left opaque and no output schema, an agent still cannot determine what inputs this node expects or what it returns, which is the core gap for a 4-parameter compute node.

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 baseline is 3. The description adds nothing beyond the schema for compute (the schema's own enum text is actually richer), and for the critical policy_parameters object it punts entirely with 'See the tool's manifest for field names', leaving the actual decision inputs unknown.

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

Purpose3/5

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

It names a specific resource (x402 V2 batch settlement) and an action, but spends most of its words on compute plumbing (server/browser delegation, kernel registration) rather than what the reconciler actually decides. It also fails to distinguish itself from near-neighbours in the sibling list such as model_x402_settlement, decode_x402_payment, or recompute_x402_eip712_digest.

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?

There is no explicit when-to-use or when-not statement. The only routing signal is the upstream/downstream artifact listing (art-03 modeler, art-60 runtime fit in; art-62 receipt verifier, cry-04/05 out), which implies placement in a chain but leaves the agent to infer when this node is the right choice.

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

All AINumbers Fintech Intelligence Suite toolsInspect
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