Skip to main content
Glama

zato crypto data

Approvals report: which contracts can still spend a wallet's top tokens (open ERC-20 allowances)

approvals_report
Read-only

Which contracts can still spend this wallet's tokens (open ERC-20 allowances, Ethereum/Base, recent window). Price: $0.003 USDC per call (x402, 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": {
      "address": "<address>"
    },
    "name": "approvals_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYeswallet (owner) address or ENS/Basename (vitalik.eth, name.base.eth)
networkNo"ethereum" (default) or "base"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower. The description still adds real behavioral facts the annotations don't: the call is paid ($0.003 USDC via x402 on Base) and results are bounded to a 'recent window' rather than all history.

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?

Two tight sentences, front-loaded with what the agent gets, followed by scope parenthetical and cost. No filler and nothing redundant with the schema.

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

Completeness4/5

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

For a read-only, two-parameter report with no output schema, the description adequately conveys what is returned, on which chains, at what cost, and with a recency limitation. Remaining gaps are the undefined 'recent window' length and no indication of result volume or 'top tokens' truncation despite the title implying a subset.

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%, so address/ENS handling and the ethereum|base network option are already documented. The description adds only the chain framing and the vague 'recent window' scope, which belongs to behavior rather than a parameter; baseline 3 applies.

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 precise question the tool answers (which contracts can still spend this wallet's tokens) and names the underlying mechanism (open ERC-20 allowances) plus chain scope. This is specific enough to separate it from siblings like token_risk, wallet_report, or counterparty_report without opening another schema.

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

Usage Guidelines3/5

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

Usage is implied by the framing (use it to audit live allowances), but there is no explicit when-to-use/when-not, no named alternative, and no prerequisites such as the wallet needing prior approval history. The chain scope and 'recent window' note give useful context but not 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.

Resources