Anyway Possible Agent Utilities

Agent Payment Safety ($0.01 USDC)

payment_guard

Read-only

Use for agent payment safety: validate a live x402 challenge, price, Base network, USDC asset, recipient, funding, gas reserve, and destination immediately before signing.

Input Schema

TableJSON Schema

Name	Required	Description
`serviceUrl`	Yes	Public HTTPS endpoint whose live x402 payment challenge should be validated.
`payerAddress`	Yes	Base wallet address that would sign and fund the x402 payment.
`expectedPayTo`	No	Optional recipient address that the payment challenge must match.
`maxAmountUsdc`	Yes	Maximum acceptable USDC charge as a decimal string.
`minGasReserveEth`	No	Optional minimum ETH balance to preserve for Base gas.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`asset`	Yes
`alerts`	Yes
`checks`	Yes
`network`	Yes
`decision`	Yes
`riskLevel`	Yes
`safeToSign`	Yes
`quotedPayTo`	Yes
`quotedAmountUsdc`	Yes
`recommendedAction`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 9, 2026

removedInput schema / properties / expectedPayTo / $ref
```
Removed value: -"#/properties/payerAddress"
```

addedInput schema / properties / expectedPayTo / description

Added value: +"Optional recipient address that the payment challenge must match."

addedInput schema / properties / expectedPayTo / pattern
```
Added value: +"^0x[a-fA-F0-9]{40}$"
```
addedInput schema / properties / expectedPayTo / type
```
Added value: +"string"
```

addedInput schema / properties / maxAmountUsdc / description

Added value: +"Maximum acceptable USDC charge as a decimal string."

addedInput schema / properties / minGasReserveEth / description

Added value: +"Optional minimum ETH balance to preserve for Base gas."

addedInput schema / properties / payerAddress / description

Added value: +"Base wallet address that would sign and fund the x402 payment."

addedInput schema / properties / serviceUrl / description

Added value: +"Public HTTPS endpoint whose live x402 payment challenge should be validated."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "alerts": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "asset": {
+      "type": "string"
+    },
+    "checks": {
+      "items": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "decision": {
+      "enum": [
+        "safe_to_sign",
+        "needs_funding",
+        "review_recipient",
+        "reject"
+      ],
+      "type": "string"
+    },
+    "network": {
+      "type": "string"
+    },
+    "quotedAmountUsdc": {
+      "type": "string"
+    },
+    "quotedPayTo": {
+      "type": "string"
+    },
+    "recommendedAction": {
+      "type": "string"
+    },
+    "riskLevel": {
+      "enum": [
+        "low",
+        "medium",
+        "high"
+      ],
+      "type": "string"
+    },
+    "safeToSign": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "decision",
+    "safeToSign",
+    "riskLevel",
+    "quotedAmountUsdc",
+    "quotedPayTo",
+    "network",
+    "asset",
+    "checks",
+    "alerts",
+    "recommendedAction"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4/5.0

Behavior4/5

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

The description discloses that validation is live and covers the full set of checks, aligning with readOnlyHint and openWorldHint. It goes beyond the annotations by specifying what gets validated (challenge, price, network, asset, recipient, funding, gas, destination) and the intended moment of use. No contradiction with annotations.

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

Conciseness5/5

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

One tightly worded sentence front-loads the purpose and follows it with a compact list of validated dimensions. There is no filler or repetition; every clause earns its place.

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?

With full schema coverage, a rich output schema, and annotations indicating a read-only open-world check, the description supplies the missing contextual essentials: when to call it and what it verifies. It could be slightly more explicit about the tool not performing the signing itself, but the readOnlyHint already covers that.

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 schema already documents every parameter. The description's enumeration of checks reinforces how parameters map to safety concerns but adds little 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 description names a specific action ('validate') applied to a live x402 payment challenge and enumerates the exact safety dimensions verified (price, Base network, USDC asset, recipient, funding, gas reserve, destination). It clearly identifies the tool as a pre-signing payment-safety guard, though it does not explicitly contrast itself with sibling tools such as treasury_preflight.

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 states a clear use condition: use 'immediately before signing' an agent payment, and scopes it to payment-safety validation. It does not name exclusions or alternative tools, but the timing and purpose provide enough context to select this tool for pre-signing checks.

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

All Anyway Possible Agent Utilities tools Inspect

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.