Skip to main content
Glama

AINumbers Fintech Intelligence Suite

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/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Verifies an AP2 v0.2 PaymentReceipt against its signed Intent/Cart/Payment mandate chain, and applies the Human-Not-Present (HNP) autonomy guardrail: amount, category, mandate age, cart freshness. Outputs: authorized_amount_headroom, findings, hnp_verdict, human_present, mandate_chain_intact, note, receipt_id, receipt_verdict, signature_check, status_asof. Output schema: call describe_tool("verify_ap2_payment_receipt").

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": "verify_ap2_payment_receipt"
  }
}

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: +{
      +  "hnp_policy": {},
      +  "mandate_chain": {},
      +  "payment_receipt": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. 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
  4. 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"
      +}
  5. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered; the description adds real value on top: determinism, server-side vs browser delegation semantics, 'gpu:true nodes always delegate', transient non-retention of inputs, and execution_hash chaining in the exported artifact. Against that, it omits failure behavior (what happens on a non-intact mandate chain or failed signature_check), which matters for a verifier.

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?

Structure is poor: 'OpenChainGraph compute node (attestation_mandate). Deterministic OpenChainGraph compute node.' repeats itself in the first two sentences, and the actual purpose appears only at the end. Large blocks are low-value for tool selection – a 64-character FV-status hash URL, an 'Open at:' documentation link, boilerplate compute-mode text duplicating the schema, and an output field dump that ends in a 'call describe_tool' redirect.

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, listing the return fields (hnp_verdict, mandate_chain_intact, signature_check, etc.) is genuinely useful and the purpose is stated. What is missing is the shape of the three nested policy_parameters sub-objects, which are declared with empty schemas, leaving the primary decision inputs undocumented. The FV-status snapshot note is irrelevant to invocation and consumes space that the missing parameter detail needed.

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 coverage is nominally 100%, so the baseline is 3, and the description adds some meaning: the four HNP guardrail dimensions (amount, category, mandate age, cart freshness) hint at what belongs in policy_parameters.hnp_policy, and the named upstream artifact IDs clarify what parent_hashes should carry. But the nested objects hnp_policy, mandate_chain and payment_receipt are declared as empty schemas with no type or key information anywhere, so the agent still cannot construct them without calling describe_tool.

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:' sentence gives a concrete verb+resource: verifies an AP2 v0.2 PaymentReceipt against its signed Intent/Cart/Payment mandate chain and applies an HNP autonomy guardrail. That is specific enough to distinguish it from generic validators. However, it never names or contrasts the near-identical siblings (validate_ap2_mandate_chain, validate_ap2_mandate_credential, authorize_payment_against_mandate), and the real purpose is buried after two paragraphs of compute-mode boilerplate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not-to-use guidance and no routing against the many AP2 siblings that overlap heavily. The only usage instruction is an input-hygiene constraint ('Use synthetic or anonymised inputs only'), which governs how to call it, not when. The upstream/downstream artifact lists imply a pipeline position but never state a selection condition.

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.