Skip to main content
Glama
covalenthq

GoldRush MCP Server

by covalenthq

erc20_token_transfers

Retrieve and analyze ERC20 token transfers for any wallet address, including historical prices and transaction details across multiple blockchain networks.

Instructions

Commonly used to render the transfer-in and transfer-out of a token along with historical prices from an address. Required: chainName (blockchain network), walletAddress (wallet address). Optional: quoteCurrency for value conversion, contractAddress to filter by specific token, startingBlock/endingBlock to set range, pageSize (default 10) and pageNumber (default 0). Returns token transfer events with timestamps, values, and transaction details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNameYesThe blockchain network to query (e.g., 'eth-mainnet', 'matic-mainnet', 'bsc-mainnet').
walletAddressYesThe wallet address to get ERC20 transfers for. Passing in an ENS, RNS, Lens Handle, or an Unstoppable Domain resolves automatically.
quoteCurrencyNoCurrency to quote transfer values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency.
contractAddressYesSpecific ERC20 token contract address to filter transfers. If null, returns transfers for all ERC20 tokens.
startingBlockNoStarting block number to begin search from. Use with endingBlock to define a range.
endingBlockNoEnding block number to search until. Use with startingBlock to define a range.
pageSizeNoNumber of transfers to return per page. Default is 10, maximum is 100.
pageNumberNoPage number for pagination, starting from 0. Default is 0.

Implementation Reference

  • The tool 'erc20_token_transfers' is defined and registered here within the 'addBalanceServiceTools' function. The handler uses the 'goldRushClient.BalanceService.getErc20TransfersForWalletAddressByPage' method to execute the logic.
    server.tool(
        "erc20_token_transfers",
        "Commonly used to render the transfer-in and transfer-out of a token along with historical prices from an address. " +
            "Required: chainName (blockchain network), walletAddress (wallet address). " +
            "Optional: quoteCurrency for value conversion, contractAddress to filter by specific token, " +
            "startingBlock/endingBlock to set range, pageSize (default 10) and pageNumber (default 0). " +
            "Returns token transfer events with timestamps, values, and transaction details.",
        {
            chainName: z
                .enum(Object.values(ChainName) as [string, ...string[]])
                .describe(
                    "The blockchain network to query (e.g., 'eth-mainnet', 'matic-mainnet', 'bsc-mainnet')."
                ),
            walletAddress: z
                .string()
                .describe(
                    "The wallet address to get ERC20 transfers for. Passing in an ENS, RNS, Lens Handle, or an Unstoppable Domain resolves automatically."
                ),
            quoteCurrency: z
                .enum(Object.values(validQuoteValues) as [string, ...string[]])
                .optional()
                .describe(
                    "Currency to quote transfer values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency."
                ),
            contractAddress: z
                .string()
                .nullable()
                .describe(
                    "Specific ERC20 token contract address to filter transfers. If null, returns transfers for all ERC20 tokens."
                ),
            startingBlock: z
                .number()
                .optional()
                .describe(
                    "Starting block number to begin search from. Use with endingBlock to define a range."
                ),
            endingBlock: z
                .number()
                .optional()
                .describe(
                    "Ending block number to search until. Use with startingBlock to define a range."
                ),
            pageSize: z
                .number()
                .optional()
                .default(10)
                .describe(
                    "Number of transfers to return per page. Default is 10, maximum is 100."
                ),
            pageNumber: z
                .number()
                .optional()
                .default(0)
                .describe(
                    "Page number for pagination, starting from 0. Default is 0."
                ),
        },
        async (params) => {
            try {
                const response =
                    await goldRushClient.BalanceService.getErc20TransfersForWalletAddressByPage(
                        params.chainName as Chain,
                        params.walletAddress,
                        {
                            quoteCurrency: params.quoteCurrency as Quote,
                            contractAddress: params.contractAddress,
                            startingBlock: params.startingBlock,
                            endingBlock: params.endingBlock,
                            pageSize: params.pageSize,
                            pageNumber: params.pageNumber,
                        }
                    );
                return {
                    content: [
                        {
                            type: "text",
                            text: stringifyWithBigInt(response.data),
                        },
                    ],
                };
            } catch (error) {
                return {
                    content: [{ type: "text", text: `Error: ${error}` }],
                    isError: true,
                };
            }
        }
    );
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. It briefly mentions the return value ('token transfer events with timestamps, values, and transaction details') but omits behavioral details like pagination limits, data availability windows, rate limiting, or whether the operation is read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured logically but inefficiently. It wastes space listing all 8 parameters with their types when the schema already provides this coverage. The opening sentence buries the lede with 'Commonly used' instead of starting with the core action.

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?

Critical flaw: The description states 'contractAddress' is optional, but the input schema marks it as required in the 'required' array. This contradiction will cause invocation failures. Additionally, with no output schema, the vague description of return values ('transaction details') is insufficient for a complex 8-parameter blockchain query tool.

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?

Input schema has 100% description coverage with clear enum values, establishing a baseline of 3. The description redundantly lists all parameters despite the schema being self-documenting, adding minimal semantic value beyond mapping 'quoteCurrency' to 'value conversion' and 'contractAddress' to filtering.

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 the tool retrieves token transfer events ('transfer-in and transfer-out') with historical prices for a specific address. However, it relies on the tool name to specify 'ERC20' rather than stating it explicitly, and uses the weak phrasing 'Commonly used to render' instead of a definitive action verb.

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?

The description provides no guidance on when to use this tool versus sibling alternatives like 'transactions_for_address' (all transactions) or 'historical_token_balances' (balance history). It merely lists parameters without explaining selection criteria or use cases.

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/covalenthq/goldrush-mcp-server'

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