Skip to main content
Glama
covalenthq

GoldRush MCP Server

by covalenthq

multichain_balances

Fetch token balances for a wallet address across multiple EVM chains in a single API call. Supports historical data, value conversion, and pagination to analyze holdings comprehensively.

Instructions

Fetch paginated spot & historical native and token balances for a single address on up to 10 EVM chains with one API call. Requires walletAddress. Optional parameters include chains array to specify networks, quoteCurrency for value conversion, limit (default 10), pagination (before), and cutoffTimestamp to filter by time. Use this to get a comprehensive view of token holdings across different blockchains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletAddressYesThe wallet address to get token balances for. Must be a valid blockchain address.
quoteCurrencyNoCurrency to quote token values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency.
beforeNoPagination cursor to get balances before this point. Use the 'before' value from previous response.
limitNoMaximum number of token balances to return. Default is 10, maximum is 100.
chainsNoArray of blockchain networks to query balances from. Can be chain names or chain IDs. If not specified, queries all supported chains.
cutoffTimestampNoUnix timestamp to filter balances by last activity. Only returns tokens with activity after this time.

Implementation Reference

  • The handler function that executes the multichain_balances tool using the GoldRush client.
    async (params) => {
        try {
            const response =
                await goldRushClient.AllChainsService.getMultiChainBalances(
                    params.walletAddress,
                    {
                        quoteCurrency: params.quoteCurrency as Quote,
                        before: params.before,
                        limit: params.limit,
                        chains: params.chains as ChainID[] | ChainName[],
                        cutoffTimestamp: params.cutoffTimestamp,
                    }
                );
            return {
                content: [
                    {
                        type: "text",
                        text: stringifyWithBigInt(response.data),
                    },
                ],
            };
        } catch (error) {
            return {
                content: [{ type: "text", text: `Error: ${error}` }],
                isError: true,
            };
        }
    }
  • Zod schema definition for the input parameters of the multichain_balances tool.
    {
        walletAddress: z
            .string()
            .describe(
                "The wallet address to get token balances for. Must be a valid blockchain address."
            ),
        quoteCurrency: z
            .enum(Object.values(validQuoteValues) as [string, ...string[]])
            .optional()
            .describe(
                "Currency to quote token values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency."
            ),
        before: z
            .string()
            .optional()
            .describe(
                "Pagination cursor to get balances before this point. Use the 'before' value from previous response."
            ),
        limit: z
            .number()
            .optional()
            .default(10)
            .describe(
                "Maximum number of token balances to return. Default is 10, maximum is 100."
            ),
        chains: z
            .array(
                z.union([
                    z.enum(
                        Object.values(ChainName) as [string, ...string[]]
                    ),
                    z.number(),
                ])
            )
            .optional()
            .describe(
                "Array of blockchain networks to query balances from. Can be chain names or chain IDs. If not specified, queries all supported chains."
            ),
        cutoffTimestamp: z
            .number()
            .optional()
            .describe(
                "Unix timestamp to filter balances by last activity. Only returns tokens with activity after this time."
            ),
    },
  • Registration of the multichain_balances tool within the MCP server instance.
    server.tool(
        "multichain_balances",
        "Fetch paginated spot & historical native and token balances for a single address on up to 10 EVM chains with one API call. " +
            "Requires walletAddress. Optional parameters include chains array to specify networks, " +
            "quoteCurrency for value conversion, limit (default 10), pagination (before), " +
            "and cutoffTimestamp to filter by time. " +
            "Use this to get a comprehensive view of token holdings across different blockchains.",
Behavior4/5

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

With no annotations provided, description carries full burden and discloses key traits: pagination mechanics ('before' cursor), limit constraints ('up to 10 EVM chains', 'default 10'), and performance characteristic ('one API call'). Missing explicit error handling or return structure disclosure.

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?

Three sentences efficiently structured: first establishes core capability and constraints, second catalogs parameters with defaults, third provides usage context. No redundant words; information density is high with all content front-loaded.

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

Completeness4/5

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

Appropriately complete for a 6-parameter tool with 100% schema coverage. Addresses pagination complexity (critical for this endpoint) and chain limits. Lacks output schema description, but this is less critical given the input complexity is well-documented and output schema is absent from spec.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage, establishing baseline 3. Description adds value by organizing parameters into required vs optional groups, highlighting the walletAddress requirement, and contextualizing quoteCurrency as 'value conversion' and cutoffTimestamp as 'filter by time', aiding agent comprehension beyond raw schema.

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?

Description uses specific verb 'Fetch' with clear resource 'spot & historical native and token balances', scope 'single address on up to 10 EVM chains', and differentiates from siblings like token_balances (single chain) and native_token_balance by emphasizing 'multichain' and 'comprehensive view across different blockchains'.

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?

Provides implied usage guidance ('Use this to get a comprehensive view of token holdings across different blockchains') suggesting when to use it (multichain scenarios), but lacks explicit 'when not to use' guidance or named alternatives like token_balances for single-chain queries.

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