Skip to main content
Glama

Wallet Doctor

approvals

Read-only

SPL token approvals: token accounts with an active delegate (SPL Token + Token-2022) — $0.0005 USDC per call via x402 v2 (Solana or Base).

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": "approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description does add genuinely non-structured behavior: a per-call price of $0.0005 USDC via x402 v2 payable on Solana or Base, plus coverage of both the legacy and Token-2022 programs. It stops short of noting rate limits, pagination, or whether a zero approval count is possible for a valid wallet.

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?

A single dense sentence, front-loaded with the resource and followed by program scope and pricing; nothing is redundant. The em-dash-and-parenthetical construction makes the payment clause run together with the data description, but no sentence is wasted.

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?

For a one-parameter read tool whose annotations already carry the safety profile, the core is present: what is returned, which token programs, and the cost model. The gaps are the meaning of wallet and the absence of any guidance on result shape beyond 'accounts with a delegate', which leaves the agent guessing about the parameter before calling.

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% for the single wallet parameter, and the description never clarifies whose wallet it is — token owner, delegate, or queried authority — nor whether it accepts a base58 address only. With the schema doing no work here, the description should compensate and does not.

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 — token accounts holding an active delegate, across both SPL Token and Token-2022 — which an agent can distinguish from a plain balance or safety check. The verb is implicit (a listing/audit of approvals), but the scope of what is returned is concrete enough to act on.

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 when-to-use or when-not-to-use guidance and no named alternative among balance, drainForensics, tokenSafety, or txtrace. The agent must infer that this is the approval-auditing tool rather than a general safety score, with nothing in the text confirming or excluding that reading.

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.

Resources