Skip to main content
Glama

AINumbers Fintech Intelligence Suite

by co.ainumbers
OverviewDiscussionsAdmin

AP2 PaymentReceipt Verifier & HNP Guardrail

verify_ap2_payment_receipt
Read-onlyIdempotent

AP2 PaymentReceipt Verifier & HNP Guardrail: OpenChainGraph compute node (attestation_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-01-ap2-mandate-chain-validator, art-60-agent-economy-runtime-fit-diagnostic, art-61-x402-batch-settlement-reconciler. Output feeds: art-01-ap2-mandate-chain-validator, art-30-agent-commerce-conformance-validator, cry-05-agent-action-audit-trail-aggregator. Open at: https://ainumbers.co/chaingraph/art-62-ap2-payment-receipt-verifier.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("verify_ap2_payment_receipt").

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": {
-    "authorized_amount_headroom": {
-      "type": "string"
-    },
-    "findings": {
-      "items": {
-        "properties": {
-          "check": {
-            "type": "string"
-          },
-          "detail": {
-            "type": "string"
-          },
-          "result": {
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "hnp_verdict": {
-      "type": "string"
-    },
-    "human_present": {
-      "type": "boolean"
-    },
-    "mandate_chain_intact": {
-      "type": "boolean"
-    },
-    "note": {
-      "type": "string"
-    },
-    "receipt_id": {
-      "type": "string"
-    },
-    "receipt_verdict": {
-      "type": "string"
-    },
-    "signature_check": {
-      "type": "string"
-    },
-    "status_asof": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "authorized_amount_headroom": {
+      "type": "string"
+    },
+    "findings": {
+      "items": {
+        "properties": {
+          "check": {
+            "type": "string"
+          },
+          "detail": {
+            "type": "string"
+          },
+          "result": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "hnp_verdict": {
+      "type": "string"
+    },
+    "human_present": {
+      "type": "boolean"
+    },
+    "mandate_chain_intact": {
+      "type": "boolean"
+    },
+    "note": {
+      "type": "string"
+    },
+    "receipt_id": {
+      "type": "string"
+    },
+    "receipt_verdict": {
+      "type": "string"
+    },
+    "signature_check": {
+      "type": "string"
+    },
+    "status_asof": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds meaningful behavior beyond that: inputs are processed transiently and not stored or logged, execution is deterministic, browser mode returns a delegation URL instead of computing, and an execution_hash artifact is exported for provenance.

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 purpose statement is front-loaded, but the body then dumps raw infrastructure detail, artifact IDs, a long URL and a full SHA-256 snapshot reference. Several sentences (fv-status snapshot caveat, output-schema pointer) could be trimmed or deferred, making it longer than needed for selection.

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?

For a nested-parameter compute node with no output schema, the description covers compute modes, privacy, chaining and versioning, and points to describe_tool for the output shape. What it omits is the substance of the verification itself – the conditions under which a receipt is judged valid or rejected – which is the key thing an agent needs.

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 all four parameters (compute, parent_hashes, parent_tool_ids, policy_parameters) are already documented in the schema. The description restates the compute-mode default but adds no new syntax or constraints for the chaining/hash parameters, so the baseline 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 name and opening line state a specific verb+resource (verify an AP2 PaymentReceipt, act as HNP guardrail) and it distinguishes itself from siblings by emitting an AP2 artifact with execution_hash for chain provenance. However, much of the body is about compute plumbing rather than what the verification actually decides, so the core purpose is clear but partly buried.

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 gives context for the compute modes (auto/server/browser, gpu:true always delegates) and an input constraint (use synthetic or anonymised inputs only), plus upstream/downstream artifact relationships. But it never states when to use this verifier versus adjacent tools like validate_ap2_mandate_credential or validate_ap2_mandate_chain, leaving the routing decision implicit.

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