Skip to main content
Glama

BRAINIAC Base Chain Data

Get ERC-20 transfers

chain-data_token_erc20-transfers

Retrieve ERC-20 Transfer events for a token contract or wallet on Base Mainnet over a bounded block range. Price $0.05 USDC. POST /api/v1/chain-data/token/erc20-transfers. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chain-data_token_erc20-transfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
toBlockNo
fromBlockNo
tokenAddressNo
walletAddressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided the description carries the full burden, and it does add real context the schema cannot: a $0.05 USDC price and the fact that unpaid calls return 402 without executing. However, it is silent on result ordering, pagination past the 1000 limit, and what happens if neither tokenAddress nor walletAddress is supplied, which matters since zero parameters are marked required.

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?

Four short sentences with the core purpose front-loaded, followed by cost, route, and failure mode. The endpoint path is slightly redundant with the tool name but is cheap and operationally useful.

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

Completeness2/5

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

For a 5-parameter tool with no annotations, no output schema, and 0% schema coverage, the description omits too much: the shape of returned transfers, behavior with no filter supplied, and pagination/ordering semantics are all left to inference.

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%, so the description must compensate and only partially does: it names the token-contract and wallet dimensions and the block range. It says nothing about `limit` (default and cap of 1000), the block-number format, or whether tokenAddress and walletAddress combine as AND or are alternatives.

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 and resource ('Retrieve ERC-20 Transfer events') plus the two filter scopes (token contract or wallet) and the network (Base Mainnet). An agent can distinguish this from siblings like erc20-balance, total-supply, or block_transactions without opening any other 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?

The phrase 'over a bounded block range' and 'for a token contract or wallet' imply how to scope a call, but there is no explicit when-to-use or when-not-to-use framing. Nothing tells the agent how this differs from logs_search for the same Transfer topic, or which filter to supply when.

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