Skip to main content
Glama

Ellimist

ERC-20 transfers

data_chain_erc20_transfers
Read-only

Use this to list recent ERC-20 Transfer events for a token, optionally only those to or from one address (up to 2,000 recent blocks): incoming/outgoing payments, flows. Price: $0.005 USDC per call via x402 (no account). Not charged if it fails.

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": {
      "token": "<token>"
    },
    "name": "data_chain_erc20_transfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoethereum
tokenYes
blocksNo
addressNo

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?

Beyond readOnlyHint/openWorldHint it adds genuinely useful operational context: the 2,000-block recency cap, the metered cost ($0.005 USDC per call via x402, no account required), and the failure-charge policy. It omits result ordering, pagination, and whether omitting address returns transfers in both directions, which leaves some behavior to inference.

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?

The use case and scope are front-loaded in one sentence, with the pricing/auth note as a separate short sentence that earns its place for a metered endpoint. Some fragmentary wording ('incoming/outgoing payments, flows') and the parenthetical block cap could be tightened slightly.

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 read-only, single-object-return list tool with no output schema, the description covers purpose and pricing but is silent on chain selection, token identifier format, and the shape/ordering of the returned transfer list. An agent can call it, but not confidently predict or parameterize the result on a non-default chain.

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 description coverage is 0%, so the description must carry parameter meaning: it clarifies address is an optional direction filter and implies blocks bounds the look-back window. However, it says nothing about the chain parameter (seven-value enum, default ethereum) and does not specify whether token is a contract address or a symbol, leaving two of four parameters under-explained.

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?

The description gives a specific verb and resource ('list recent ERC-20 Transfer events for a token') plus the filter scope ('only those to or from one address') and a concrete window cap ('up to 2,000 recent blocks'). That is enough for an agent to tell this apart from chain-account or DeFi-sibling tools without opening the schema.

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?

It opens with an explicit 'Use this to...' directive and names the concrete use cases (incoming/outgoing payments, flows), and it explains the optional address filter so the agent knows how to narrow the query. It stops short of stating when NOT to use it or naming an alternative such as the chain-account sibling, so it is clear context without exclusions.

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