Skip to main content
Glama

PayStage — x402 payment safety and spend policy

list_outstanding_auths

Read-only

spending limits. Call this when auditing what an agent could still spend without a new signature — ERC-20 allowances, Permit2 and EIP-3009 authorisations. Returns each authorisation with spender, amount and expiry. Read-only and needs only a public RPC; no key, no funds moved. Use it after an incident to see what remains exposed, not to revoke anything (this tool cannot revoke).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wallet": "<wallet>"
    },
    "name": "list_outstanding_auths"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyNo
tokensNo
walletYes
networkNo
rpc_urlNo
spendersNo
policy_pathNo
eip3009_noncesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered; the description still earns credit by adding operational context beyond them — a public RPC is sufficient, no key is required, no funds move, and it cannot revoke. It also sketches the return shape (spender, amount, expiry). Minor gaps: no mention of pagination or volume limits for wallets with many authorisations.

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

Conciseness3/5

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

The body is dense and front-loaded with the safety and scope facts, which is good. The opening fragment 'spending limits.' looks like truncated text and wastes the highest-attention position. Sentences otherwise earn their place with little filler.

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

Completeness2/5

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

For a tool with 8 parameters, 0% schema coverage and no output schema, the description is thin where it matters most: the caller is told what comes back at a high level but not what any input does or which are required. It compensates well on safety and intent, but an agent could not correctly construct a call from this text plus an undocumented schema.

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?

Schema description coverage is 0% across 8 parameters, so the description must carry the burden and largely does not: wallet, network, rpc_url, policy, policy_path, tokens, spenders and eip3009_nonces are never explained. The only implicit mapping is that ERC-20/Permit2/EIP-3009 appear, hinting at the tokens/spenders/eip3009_nonces filters, but an agent gets no guidance on how these narrow the scan or how policy/policy_path interact with the listing.

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 resource — outstanding token authorisations — and enumerates the concrete kinds it covers (ERC-20 allowances, Permit2, EIP-3009), so an agent knows exactly what is listed. It does not, however, distinguish itself from the sibling evaluate_outstanding_auths, which reads as a near-identical target. The dangling opener 'spending limits.' is a truncated fragment that adds no clarity.

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 gives a clear triggering context ('when auditing what an agent could still spend without a new signature', 'after an incident to see what remains exposed') and an explicit exclusion ('not to revoke anything — this tool cannot revoke'). What is missing is routing to the obvious alternative: the sibling evaluate_outstanding_auths is never mentioned, so the agent must infer when to list versus when to evaluate.

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.