Skip to main content
Glama

AINumbers Fintech Intelligence Suite

by co.ainumbers
OverviewDiscussionsAdmin

Agentic Payments Protocol Comparator

compare_agentic_rail_protocols
Read-onlyIdempotent

Agentic Payments Protocol Comparator: OpenChainGraph compute node (routing_policy). 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. Output feeds: art-16-google-ap2-mandate-builder, art-23-visa-trusted-agent-protocol-inspector, art-24-mastercard-agentic-token-builder, art-25-a2a-agent-card-validator, art-26-x402-payload-decoder-flow-simulator, ptg-01-ap2-prompt-template-generator. Open at: https://ainumbers.co/chaingraph/art-22-agentic-payments-protocol-comparator.html FV-status (published/proven/still-trusted for this spec): /fv-status/ca4e1dca8343f788a296161f0e19712f7afb7e5eaec0431081e715a4cc34b784.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Compares AP2, ACP, x402, Visa TAP, Mastercard Agentic Token, and Tempo MPP (Machine Payments Protocol) across 8 dimensions (backer, artifact, signing, scope, rail, identity, audit, status) and 6 agentic scenarios. Outputs: crosswalk, note, protocol_names, protocols_compared, protocols_detail, recommendation, scenario. Output schema: call describe_tool("compare_agentic_rail_protocols").

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". Required: protocols. 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\". Required: protocols. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
+  "protocols": {
+    "type": "array"
+  },
+  "scenario": {}
+}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
-  "type": "string"
-}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "crosswalk": {
-      "items": {
-        "properties": {
-          "concept": {
-            "type": "string"
-          },
-          "values": {
-            "properties": {
-              "acp": {
-                "type": "string"
-              },
-              "ap2": {
-                "type": "string"
-              }
-            },
-            "type": "object"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "note": {
-      "type": "string"
-    },
-    "protocol_names": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "protocols_compared": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "protocols_detail": {
-      "items": {
-        "properties": {
-          "artifact": {
-            "type": "string"
-          },
-          "audit": {
-            "type": "string"
-          },
-          "backer": {
-            "type": "string"
-          },
-          "id": {
-            "type": "string"
-          },
-          "identity": {
-            "type": "string"
-          },
-          "name": {
-            "type": "string"
-          },
-          "rail": {
-            "type": "string"
-          },
-          "scope": {
-            "type": "string"
-          },
-          "signed": {
-            "type": "string"
-          },
-          "status": {
-            "type": "string"
-          },
-          "sub": {
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "recommendation": {
-      "properties": {
-        "also_consider": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "also_names": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "primary_names": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "primary_pick": {
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "rationale": {
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "scenario": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "crosswalk": {
+      "items": {
+        "properties": {
+          "concept": {
+            "type": "string"
+          },
+          "values": {
+            "properties": {
+              "acp": {
+                "type": "string"
+              },
+              "ap2": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "protocol_names": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "protocols_compared": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "protocols_detail": {
+      "items": {
+        "properties": {
+          "artifact": {
+            "type": "string"
+          },
+          "audit": {
+            "type": "string"
+          },
+          "backer": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "identity": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "rail": {
+            "type": "string"
+          },
+          "scope": {
+            "type": "string"
+          },
+          "signed": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "sub": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "recommendation": {
+      "properties": {
+        "also_consider": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "also_names": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "primary_names": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "primary_pick": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "rationale": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "scenario": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  5. Added

TDQS

B3.2/5.0
Behavior4/5

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

Beyond readOnlyHint/idempotentHint, the description discloses that execution is deterministic, that compute:"auto" runs server-side on Cloudflare Workers for gpu:false kernels while compute:"browser" returns a delegation URL, and that gpu:true nodes always delegate. It also states inputs are processed transiently and not stored or logged, warns to use synthetic/anonymised inputs only, and notes the export carries execution_hash for chain provenance.

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 real purpose statement arrives after a long preamble of routing_policy, privacy, downstream-feed IDs, a raw URL, and an FV-status hash that an agent does not need in order to call the tool. Front-loading is inverted: the most useful sentence is last.

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

Completeness4/5

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

Despite the clutter, the definition covers the essentials for a read-only comparison node: what is compared, the compute/delegation modes, privacy posture, provenance export, enumerated output fields (crosswalk, protocols_detail, recommendation, scenario), and a describe_tool pointer. Only the sibling disambiguation is missing.

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 compute enum, parent_hashes chaining, and policy_parameters requirements are already documented. The description restates the compute default and the 'protocols is required, unknown keys refused' rule, plus the gpu:true delegation exception, but adds little syntax or format detail beyond the schema.

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 gives a precise verb and resource: comparing AP2, ACP, x402, Visa TAP, Mastercard Agentic Token and Tempo MPP across 8 dimensions and 6 scenarios, with named outputs. However, it is buried at the end of infrastructure boilerplate, and no distinction is drawn against the near-identical sibling compare_agentic_payment_protocols or crosswalk_agent_payment_rail_trust.

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?

The description never says when to pick this comparator rather than compare_agentic_payment_protocols, select_agentic_checkout_protocol, or crosswalk_agent_payment_rail_trust. The only routing guidance is about compute mode (auto/server/browser), not about tool selection, so the agent must guess.

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