Skip to main content
Glama
PayStage MCP Server

PayStage MCP Server

evaluate_outstanding_auths

List and evaluate outstanding token authorizations against a policy to flag double-pay or limbo risk before approving payments.

Instructions

List and evaluate outstanding token authorizations against a policy

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

C2.4/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and does not meet it: it does not say whether evaluation is read-only, what happens to flagged authorizations, whether it requires an RPC endpoint, or what form the evaluation takes. Only the vague notion of comparing against a policy is conveyed.

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?

It is a single front-loaded sentence with no wasted words, which is good, but the brevity comes at the cost of under-specification rather than efficiency. For an 8-parameter tool the sentence is too thin to structure the call.

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

Completeness1/5

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

With no annotations, no output schema, and no per-parameter documentation, the single sentence is far from sufficient for an 8-parameter tool whose output semantics (what an "evaluation" looks like) are undefined. An agent cannot confidently invoke it from this definition.

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, and the description only references "policy" without explaining tokens, spenders, network, rpc_url, policy_path, or eip3009_nonces. None of the ambiguous inputs gain meaning from the description.

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 verb pair ("List and evaluate") and a specific resource ("outstanding token authorizations"), and the policy-comparison scope distinguishes it from the sibling list_outstanding_auths, which only lists. It stops short of explaining what "evaluate" produces, so it is clear but not fully self-contained.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus list_outstanding_auths, nor of prerequisites such as which network or wallet must be supplied first. Usage is only implied by the phrase "against a policy", leaving the agent to guess.

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