Skip to main content
Glama

approval_scan

Read-onlyIdempotent

Scan a wallet for risky token approvals. On EVM chains: identifies unlimited ERC-20 approvals and unverified spenders. On Solana: scans SPL token delegate authorities. Returns risk assessment. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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": {
      "address": "<address>"
    },
    "name": "approval_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain network (includes Solana support)ethereum
addressYesWallet address to scan (0x-prefixed for EVM, base58 for Solana)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds material context beyond annotations: the 10-call/day free quota and the x402 pay-per-call fallback, plus what specific risks are detected per chain.

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?

Four sentences, front-loaded with purpose, then chain specifics, return type, and quota. No wasted words; each sentence adds distinct information.

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

Completeness5/5

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

For a read-only scan with rich annotations and a fully described two-parameter schema, the description supplies purpose, chain behavior, return summary, and quota limits. No output schema exists, but the description's 'returns risk assessment' is sufficient for this tool's complexity.

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 coverage is 100% with an enum for chain and a described address format, so the schema carries parameter meaning. The description only echoes chain-specific scanning behavior and does not add syntax or format details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Scan') and resource ('wallet for risky token approvals'), then details chain-specific detection: unlimited ERC-20 approvals, unverified spenders, and SPL delegate authorities. This distinguishes it from broader siblings like wallet_safety by focusing narrowly on approval risk.

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?

Provides clear context for when to use it—checking token approval risk on EVM or Solana—but does not name alternatives or state exclusions (e.g., when to prefer wallet_safety or risk_batch). The chain-specific breakdown helps an agent self-select, but explicit routing guidance is absent.

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.