Skip to main content
Glama
covalenthq

GoldRush MCP Server

by covalenthq

multichain_address_activity

Analyze wallet activity across multiple blockchain networks to identify active chains, transaction counts, and activity timestamps with a single API call.

Instructions

Commonly used to locate chains which an address is active on with a single API call. Requires walletAddress. Optional parameter testnets (default false) determines whether to include testnet activity. Returns a comprehensive summary of chain activity including transaction counts, first/last activity timestamps, and activity status across all networks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletAddressYesThe wallet address to analyze activity for. Passing in an ENS, RNS, Lens Handle, or an Unstoppable Domain resolves automatically.
testnetsNoWhether to include testnet activity in the analysis. Default is false (mainnet only).

Implementation Reference

  • Registration and handler implementation for the multichain_address_activity tool. It uses the Covalent GoldRush SDK's AllChainsService.getAddressActivity method.
    server.tool(
        "multichain_address_activity",
        "Commonly used to locate chains which an address is active on with a single API call. " +
            "Requires walletAddress. Optional parameter testnets (default false) " +
            "determines whether to include testnet activity. " +
            "Returns a comprehensive summary of chain activity including transaction counts, " +
            "first/last activity timestamps, and activity status across all networks.",
        {
            walletAddress: z
                .string()
                .describe(
                    "The wallet address to analyze activity for. Passing in an ENS, RNS, Lens Handle, or an Unstoppable Domain resolves automatically."
                ),
            testnets: z
                .boolean()
                .optional()
                .default(false)
                .describe(
                    "Whether to include testnet activity in the analysis. Default is false (mainnet only)."
                ),
        },
        async (params) => {
            try {
                const response =
                    await goldRushClient.AllChainsService.getAddressActivity(
                        params.walletAddress,
                        { testnets: params.testnets }
                    );
                return {
                    content: [
                        {
                            type: "text",
                            text: stringifyWithBigInt(response.data),
                        },
                    ],
                };
            } catch (error) {
                return {
                    content: [{ type: "text", text: `Error: ${error}` }],
                    isError: true,
                };
            }
        }
    );
Behavior4/5

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

With no annotations provided, description carries full burden and successfully discloses return value structure (transaction counts, timestamps, activity status) and default behavior (testnets=false means mainnet only). Missing explicit read-only declaration, though implied by 'locate' and 'returns summary' language.

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 well-structured sentences: purpose (locate chains), parameters (requirements and defaults), and output (comprehensive summary contents). Front-loaded with primary use case, zero redundant words, appropriate length for 2-parameter tool.

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

Completeness5/5

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

No output schema exists, but description compensates by detailing return contents (transaction counts, timestamps, status). Combined with 100% schema coverage for inputs and clear scope definition, the description is complete for this complexity level.

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 coverage is 100%, establishing baseline 3. Description emphasizes required vs optional status ('Requires walletAddress. Optional parameter testnets...') but adds no semantic detail beyond what schema already provides regarding ENS/RNS resolution or testnet inclusion logic.

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 clearly states the tool 'locate chains which an address is active on' - specific verb (locate) + resource (chains) + scope (address activity). The phrase 'single API call' distinguishes it from potentially more verbose alternatives like multichain_transactions.

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 context by specifying it locates chain activity (discovering presence vs fetching detailed balances/transactions), but lacks explicit when-to-use guidance or comparison to siblings like multichain_balances or transactions_for_address.

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