Skip to main content
Glama

AgentResolver — Agent Commerce Health Monitoring

by io.github.waxsway
OverviewDiscussionsAdmin

x402 settlement test — wallet facilitator payment test — $0.001

x402_ping
Read-only

Paid $0.001 USDC on Base or Solana no-body settlement canary for funded agents. Returns a timestamped pong only after successful x402 payment to verify wallet, facilitator, payment, and delivery end-to-end.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
echoNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
atYes
echoYes
nextYes
pongYes
unixMsYes
requestIdYes
settledDeliveryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed2 schema fields changed
    • addedOutput schema / properties / next / properties / settlementVerify
      Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "capabilityId": {
+      "type": "string"
+    },
+    "endpoint": {
+      "format": "uri",
+      "type": "string"
+    },
+    "inputExample": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "method": {
+      "const": "GET",
+      "type": "string"
+    },
+    "paymentAuthorization": {
+      "const": "separate_caller_authorization_required",
+      "type": "string"
+    },
+    "priceUsd": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "transactionHashSource": {
+      "type": "string"
+    },
+    "useWhen": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "capabilityId",
+    "endpoint",
+    "method",
+    "priceUsd",
+    "useWhen",
+    "inputExample",
+    "transactionHashSource",
+    "paymentAuthorization"
+  ],
+  "type": "object"
+}
    • changedOutput schema / properties / next / required
      Previous value: -[
-  "catalogUrl",
-  "recommended",
-  "preflight",
-  "single",
-  "batch"
-]New value: +[
+  "catalogUrl",
+  "recommended",
+  "preflight",
+  "settlementVerify",
+  "single",
+  "batch"
+]
  4. Changed2 schema fields changed
    • addedOutput schema / properties / next
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "batch": {
+      "additionalProperties": {},
+      "properties": {
+        "capabilityId": {
+          "type": "string"
+        },
+        "endpoint": {
+          "format": "uri",
+          "type": "string"
+        },
+        "inputExample": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "method": {
+          "const": "POST",
+          "type": "string"
+        },
+        "priceUsd": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "useWhen": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "capabilityId",
+        "endpoint",
+        "method",
+        "priceUsd",
+        "useWhen",
+        "inputExample"
+      ],
+      "type": "object"
+    },
+    "catalogUrl": {
+      "format": "uri",
+      "type": "string"
+    },
+    "preflight": {
+      "additionalProperties": {},
+      "properties": {
+        "capabilityId": {
+          "type": "string"
+        },
+        "endpoint": {
+          "format": "uri",
+          "type": "string"
+        },
+        "inputExample": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "method": {
+          "const": "GET",
+          "type": "string"
+        },
+        "priceUsd": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "useWhen": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "capabilityId",
+        "endpoint",
+        "method",
+        "priceUsd",
+        "useWhen",
+        "inputExample"
+      ],
+      "type": "object"
+    },
+    "recommended": {
+      "additionalProperties": {},
+      "properties": {
+        "capabilityId": {
+          "type": "string"
+        },
+        "endpoint": {
+          "format": "uri",
+          "type": "string"
+        },
+        "inputExample": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "method": {
+          "const": "GET",
+          "type": "string"
+        },
+        "paymentAuthorization": {
+          "const": "separate_caller_authorization_required",
+          "type": "string"
+        },
+        "priceUsd": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "reason": {
+          "type": "string"
+        },
+        "repeatUse": {
+          "type": "string"
+        },
+        "useWhen": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "capabilityId",
+        "endpoint",
+        "method",
+        "priceUsd",
+        "useWhen",
+        "inputExample",
+        "reason",
+        "repeatUse",
+        "paymentAuthorization"
+      ],
+      "type": "object"
+    },
+    "single": {
+      "additionalProperties": {},
+      "properties": {
+        "capabilityId": {
+          "type": "string"
+        },
+        "endpoint": {
+          "format": "uri",
+          "type": "string"
+        },
+        "inputExample": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "method": {
+          "const": "POST",
+          "type": "string"
+        },
+        "priceUsd": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "useWhen": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "capabilityId",
+        "endpoint",
+        "method",
+        "priceUsd",
+        "useWhen",
+        "inputExample"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "catalogUrl",
+    "recommended",
+    "preflight",
+    "single",
+    "batch"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "pong",
-  "settledDelivery",
-  "at",
-  "unixMs",
-  "requestId",
-  "echo"
-]New value: +[
+  "pong",
+  "settledDelivery",
+  "at",
+  "unixMs",
+  "requestId",
+  "echo",
+  "next"
+]
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "at": {
+      "type": "string"
+    },
+    "echo": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pong": {
+      "const": true,
+      "type": "boolean"
+    },
+    "requestId": {
+      "type": "string"
+    },
+    "settledDelivery": {
+      "const": true,
+      "type": "boolean"
+    },
+    "unixMs": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "pong",
+    "settledDelivery",
+    "at",
+    "unixMs",
+    "requestId",
+    "echo"
+  ],
+  "type": "object"
+}
  6. Added

TDQS

B3.1/5.0
Behavior1/5

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

The description states the tool is 'Paid $0.001 USDC' and returns a pong 'only after successful x402 payment,' which implies the tool triggers a payment and spends funds. The annotations declare readOnlyHint=true; this contradicts the described state-changing/financial behavior, requiring a score of 1 per the contradiction rule.

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 text is compact: two sentences, with cost and the payment-gated response front-loaded. The phrase 'no-body settlement canary' is awkward but does not add significant bloat; every clause contributes.

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 an output schema present, the absence of return-value detail is acceptable. The description covers cost, chains (Base/Solana), and the payment-gated pong. It stops short of explaining failure modes, prerequisite wallet/facilitator setup, or how this differs from related tools, so it is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one optional string parameter ('echo') with 0% description coverage, and the description does not mention it at all. Because coverage is low, the description was expected to compensate, but it provides no semantic guidance beyond the parameter name and maxLength.

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 clearly identifies the tool as a paid settlement canary: 'Returns a timestamped pong only after successful x402 payment to verify wallet, facilitator, payment, and delivery end-to-end.' The verb and resource are specific, and the title reinforces the $0.001 cost and settlement-test purpose.

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?

Usage is implied: it is 'a settlement canary for funded agents' and should be used to verify the x402 payment path. However, it never names alternatives such as x402_payment_preflight or says when not to use this tool, so an agent must infer the decision boundary.

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

All AgentResolver — Agent Commerce Health Monitoring 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