Skip to main content
Glama

PayStage — x402 payment safety and spend policy

evaluate_outstanding_auths

Read-only

spending limits. Call this when an agent already holds authorisations and you need to know which are dangerous. Verdict is pay | review | do_not_pay per authorisation, with reason codes naming the rule that fired (unlimited allowance, expiry already passed, spender not on the allow-list). Returns per-authorisation decisions plus a summary action. Read-only: never revokes, never signs. Revocation is a transaction you send yourself.

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": "evaluate_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?

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by saying it never revokes or signs and that revocation is a separate transaction. It also explains the verdict taxonomy and reason codes, though it does not cover rate limits, auth requirements, or failure modes.

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 and most sentences carry useful information about usage, verdicts, and non-mutating behavior. The opening fragment 'spending limits.' is confusing and not front-loaded, but it is a minor blemish.

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?

This is a complex tool with 8 parameters and no output schema, yet the description only explains the verdict output and read-only behavior. It omits any parameter semantics and does not describe what inputs like policy, spenders, or eip3009_nonces control.

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

Parameters1/5

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

Schema description coverage is 0% across 8 parameters, including policy, tokens, spenders, policy_path, and eip3009_nonces. The description provides no parameter meaning, format, or requiredness guidance, leaving the schema entirely undocumented.

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 states a specific verb and resource: evaluating outstanding authorisations and returning pay/review/do_not_pay verdicts. It does not differentiate this tool from siblings like list_outstanding_auths or evaluate_batch, so it falls short of a 5.

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 condition for use: call when an agent already holds authorisations and you need to know which are dangerous. It does not state when not to use it or name an alternative tool, so it lacks explicit routing guidance.

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.