Skip to main content
Glama

fetchTransfers

Retrieve token and ETH transfers filtered by address, block range, or contract. Use fromBlock, toBlock, fromAddress, toAddress, contractAddresses, category, order, withMetadata, excludeZeroValue, maxCount, pageKey, and network parameters.

Instructions

Get token and ETH transfers filtered by address, block range, or contract

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromBlockNoThe block number to start the search from. e.g. "1234567890". Inclusive from block (hex string, int, latest, or indexed).0x0
toBlockNoThe block number to end the search at. e.g. "1234567890". Inclusive to block (hex string, int, latest, or indexed).latest
fromAddressNoThe wallet address to query the transfer was sent from.
toAddressNoThe wallet address to query the transfer was sent to.
contractAddressesNoThe contract addresses to query. e.g. ["0x1234567890123456789012345678901234567890"]
categoryNoThe category of transfers to query. e.g. "external" or "internal"
orderNoThe order of the results. e.g. "asc" or "desc".asc
withMetadataNoWhether to include metadata in the results.
excludeZeroValueNoWhether to exclude zero value transfers.
maxCountNoThe maximum number of results to return. e.g. "0x3E8".0xA
pageKeyNoThe cursor to start the search from. Use this to paginate through the results.
networkNoNetwork ID. Call listSupportedNetworks for all options. e.g. "eth-mainnet", "base-mainnet"eth-mainnet
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether the operation is read-only, mutating, requires authentication, or has rate limits. The single word 'Get' implies read-only, but this is not explicit.

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?

The description is a single concise sentence that accurately summarizes the tool's purpose without unnecessary words or repetition.

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 tool with no output schema, the description does not describe the return format or behavior. However, given the comprehensive input schema and straightforward read operation, the description is minimally adequate but could be improved by noting the return type.

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?

The input schema covers 100% of parameters with descriptions, so the tool description does not need to add much. It adds no extra meaning beyond the schema, resulting in a baseline score of 3.

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

Purpose4/5

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

The description clearly states 'Get token and ETH transfers filtered by address, block range, or contract', specifying the verb and resource. However, it does not explicitly distinguish this tool from sibling tools like fetchAddressTransactionHistory, which may have overlapping functionality.

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

Usage Guidelines2/5

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

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, and no exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alchemyplatform/alchemy-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server