Skip to main content
Glama

AINumbers Fintech Intelligence Suite

by co.ainumbers
OverviewDiscussionsAdmin

x402 Header Decoder, Payload Linter & 402 Flow Simulator

decode_x402_payment
Read-onlyIdempotent

Decode an x402 payment header or lint an exact-scheme PaymentPayload, and describe the HTTP-402 verify/settle flow. Use when a developer is integrating x402 and needs to inspect a header, check a payload shape, or understand the flow. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("decode_x402_payment").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputsNoMap of tool input element IDs to values (see manifest input_schema). Applied via AIN Bridge prefill.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "decoded": {
-      "type": "object"
-    },
-    "findings": {
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "decoded": {
+      "type": "object"
+    },
+    "findings": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already cover readOnlyHint, idempotentHint, and destructiveHint, and the description adds genuinely useful behavioral context: the tool runs client-side with zero PII and zero network, renders as an interactive widget, and receives inputs via the AIN Bridge. This goes beyond what annotations alone convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, front-loads the purpose, and keeps the use-case sentence immediately after. The 'Output schema: call describe_tool(...)' line is a slight indirection but is concise rather than padded.

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?

This tool has no output schema and a generic single-input wrapper, yet the description does not specify the actual input keys, expected values, or result shape. The pointer to describe_tool helps, but the description is not fully self-contained for an agent that needs to invoke it correctly without extra discovery.

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?

The input schema only describes a generic 'inputs' map and defers to a manifest input_schema, while the description does not explain actual element IDs, value formats, or how to specify a header or payload. Schema description coverage is high, so the baseline is 3, but the description adds no real parameter-level clarity.

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

Purpose5/5

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

The description states three concrete capabilities with specific verbs and resources: decode an x402 payment header, lint an exact-scheme PaymentPayload, and describe the HTTP-402 verify/settle flow. This clearly differentiates the tool from the broader x402 sibling set, and the title reinforces the same message.

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

Usage Guidelines4/5

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

It explicitly says 'Use when a developer is integrating x402 and needs to inspect a header, check a payload shape, or understand the flow,' providing a clear trigger context. It does not mention when-not-to-use or name alternative sibling tools, so it stops short of full routing guidance.

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