Skip to main content
Glama

List ERC-20 transfers for an address in recent blocks

evm_transfers
Read-only

ERC-20 transfers into and out of an address in a window of recent blocks (default 2,000, max 10,000), from Transfer logs, newest first, max 100 rows with token symbols. token limits the search to one contract. A busy address can be truncated: narrow the window to see the rest. Related tools on this server, for a different need: evm_balance when you need ERC-20 balance of an address for one token contract; evm_address when you need native balance, nonce and account type of an EVM address. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
chainNobase (default), ethereum, arbitrum, optimism or polygon
tokenNoOptional ERC-20 contract, 0x…
blocksNoBlocks to search back from the latest (max 10000)
addressYesEVM address, 0x…

Output Schema

NameRequiredDescriptionDefault
chainNo
countNo
tokenNo
sourceNo
windowNo
addressNo
checkedAtNo
transfersNo
truncatedNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnly and openWorld; the description adds real behavioral context beyond them — the underlying source (Transfer logs), newest-first ordering, an output cap of 100 rows, silent truncation on busy addresses, and a $0.003 x402 charge with failed calls uncharged. What is missing is any statement of rate limits or pagination/cursor mechanics for retrieving rows past the 100-row cap, so it falls just short of full disclosure.

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?

Front-loaded with the core behavior, then truncation warning, then sibling routing, then pricing — a sensible descending order of importance with no filler. It is dense to the point of being a single run-on clause chain, which slightly hurts scannability, but every sentence carries information an agent needs.

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?

With an output schema present, the description does not need to enumerate return fields, and it correctly spends its words on scope, caps, truncation, alternatives and cost instead. For a 4-parameter read-only query tool, an agent has everything required to decide to call it and interpret a truncated result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: a default window of 2,000 blocks (the schema only states the 10,000 max) and the constraint that 'token limits the search to one contract'. It does not clarify accepted formats for blocks or why it is typed as a string, leaving one gap.

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+resource+scope: 'ERC-20 transfers into and out of an address in a window of recent blocks', and pins the data source (Transfer logs), ordering (newest first) and result shape (max 100 rows with token symbols). It also names what it is not (evm_balance for single-token balance, evm_address for native balance/nonce), so an agent can separate it from siblings without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit routing conditions: 'evm_balance when you need ERC-20 balance of an address for one token contract' and 'evm_address when you need native balance, nonce and account type'. It also handles the in-tool edge case with 'A busy address can be truncated: narrow the window to see the rest.' Both when-to-use and recovery behavior are stated, not inferred.

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