Skip to main content
Glama
covalenthq

GoldRush MCP Server

by covalenthq

transactions_for_address

Fetch paginated transaction history for a blockchain wallet address, including decoded log events, across multiple supported networks.

Instructions

Commonly used to fetch the transactions involving an address including the decoded log events in a paginated fashion. Required: chainName (blockchain network), walletAddress (wallet address), page (page number). Optional: quoteCurrency, noLogs, blockSignedAtAsc (chronological order). Returns transactions for the specified page of results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNameYesThe blockchain network to query (e.g., 'eth-mainnet', 'matic-mainnet', 'bsc-mainnet').
walletAddressYesThe wallet address to get transactions for. Passing in an ENS, RNS, Lens Handle, or an Unstoppable Domain resolves automatically.
pageYesPage number for pagination, starting from 0. Each page contains multiple transactions.
quoteCurrencyNoCurrency to quote transaction values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency.
noLogsNoExclude event logs from transactions for faster performance. Default is true.
blockSignedAtAscNoSort transactions in ascending chronological order. Default is false (newest first).

Implementation Reference

  • The handler function for the "transactions_for_address" tool, which invokes the Covalent GoldRush SDK's getPaginatedTransactionsForAddress method and formats the response.
    async (params) => {
        try {
            const response =
                await goldRushClient.TransactionService.getPaginatedTransactionsForAddress(
                    params.chainName as Chain,
                    params.walletAddress,
                    params.page,
                    {
                        quoteCurrency: params.quoteCurrency as Quote,
                        noLogs: params.noLogs,
                        blockSignedAtAsc: params.blockSignedAtAsc,
                    }
                );
            return {
                content: [
                    {
                        type: "text",
                        text: stringifyWithBigInt(response.data),
                    },
                ],
            };
        } catch (err) {
            return {
                content: [{ type: "text", text: `Error: ${err}` }],
                isError: true,
            };
        }
    }
  • Input schema definition using Zod for the "transactions_for_address" tool.
    {
        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 transactions for. Passing in an ENS, RNS, Lens Handle, or an Unstoppable Domain resolves automatically."
            ),
        page: z
            .number()
            .describe(
                "Page number for pagination, starting from 0. Each page contains multiple transactions."
            ),
        quoteCurrency: z
            .enum(Object.values(validQuoteValues) as [string, ...string[]])
            .optional()
            .describe(
                "Currency to quote transaction values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency."
            ),
        noLogs: z
            .boolean()
            .optional()
            .default(true)
            .describe(
                "Exclude event logs from transactions for faster performance. Default is true."
            ),
        blockSignedAtAsc: z
            .boolean()
            .optional()
            .describe(
                "Sort transactions in ascending chronological order. Default is false (newest first)."
            ),
    },
  • Registration of the "transactions_for_address" tool within the MCP server instance.
    server.tool(
        "transactions_for_address",
        "Commonly used to fetch the transactions involving an address including the decoded log events in a paginated fashion.\n" +
            "Required: chainName (blockchain network), walletAddress (wallet address), page (page number).\n" +
            "Optional: quoteCurrency, noLogs, blockSignedAtAsc (chronological order).\n" +
            "Returns transactions for the specified page of results.",
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 discloses pagination behavior and inclusion of decoded log events, but fails to mention safety profile (read-only nature), rate limits, items per page, or error conditions that would help an agent invoke it correctly.

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?

Three sentences that are information-dense and front-loaded. The parameter listing in sentence two is slightly redundant with the schema but efficient for quick scanning. No fluff or unnecessary verbosity.

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?

Given the lack of output schema, the description only vaguely states 'Returns transactions for the specified page of results' without describing the structure, fields, or format of the returned data. However, with 6 fully-documented input parameters and mention of decoded logs, it meets minimum viability for a 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?

Schema description coverage is 100%, establishing a baseline of 3. The description repeats parameter names with brief parenthetical labels (e.g., 'blockchain network', 'chronological order') that mirror the schema descriptions but add no additional semantic context or usage examples beyond the structured schema.

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?

Clearly states it fetches transactions involving an address with decoded log events in a paginated fashion. The mention of 'decoded log events' and 'paginated' helps distinguish from siblings like 'transaction' (single tx) or 'log_events_by_address' (logs only), though it does not explicitly name alternatives.

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?

Lists required versus optional parameters but provides no guidance on when to use this tool versus similar siblings like 'multichain_transactions', 'bitcoin_transactions', or 'transactions_for_block'. No mention of prerequisites or conditions where this tool is preferred.

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