Skip to main content
Glama
covalenthq

GoldRush MCP Server

by covalenthq

nft_for_address

Retrieve and display NFT collections held by a wallet address on supported blockchain networks, with options to filter spam and manage metadata fetching.

Instructions

Commonly used to render the NFTs (including ERC721 and ERC1155) held by an address. Required: chainName (blockchain network name), walletAddress (wallet address or ENS/domain). Optional: noSpam (filter spam, default true), noNftAssetMetadata (exclude metadata for faster response, default true), withUncached (fetch uncached metadata, may be slower, default false). Returns complete details of NFTs in the wallet including metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNameYesThe blockchain network to query (e.g., 'eth-mainnet', 'matic-mainnet', 'bsc-mainnet').
walletAddressYesThe wallet address to get NFTs for. Can be a wallet address or ENS/domain name.
noSpamNoFilter out spam/scam NFTs from results. Default is true.
noNftAssetMetadataNoSkip fetching NFT asset metadata for faster response. Default is true.
withUncachedNoFetch uncached metadata directly from source (may be slower but more up-to-date). Default is false.

Implementation Reference

  • The "nft_for_address" tool is registered and implemented in src/services/NftService.ts. It uses the Covalent GoldRushClient to fetch NFT data and returns the result as a text content object.
    server.tool(
        "nft_for_address",
        "Commonly used to render the NFTs (including ERC721 and ERC1155) held by an address.\n" +
            "Required: chainName (blockchain network name), walletAddress (wallet address or ENS/domain).\n" +
            "Optional: noSpam (filter spam, default true), noNftAssetMetadata (exclude metadata for faster response, default true), " +
            "withUncached (fetch uncached metadata, may be slower, default false).\n" +
            "Returns complete details of NFTs in the wallet including metadata.",
        {
            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 NFTs for. Can be a wallet address or ENS/domain name."
                ),
            noSpam: z
                .boolean()
                .optional()
                .default(true)
                .describe(
                    "Filter out spam/scam NFTs from results. Default is true."
                ),
            noNftAssetMetadata: z
                .boolean()
                .optional()
                .default(true)
                .describe(
                    "Skip fetching NFT asset metadata for faster response. Default is true."
                ),
            withUncached: z
                .boolean()
                .optional()
                .default(false)
                .describe(
                    "Fetch uncached metadata directly from source (may be slower but more up-to-date). Default is false."
                ),
        },
        async (params) => {
            try {
                const response =
                    await goldRushClient.NftService.getNftsForAddress(
                        params.chainName as Chain,
                        params.walletAddress,
                        {
                            noSpam: params.noSpam,
                            noNftAssetMetadata: params.noNftAssetMetadata,
                            withUncached: params.withUncached,
                        }
                    );
                return {
                    content: [
                        {
                            type: "text",
                            text: stringifyWithBigInt(response.data),
                        },
                    ],
                };
            } catch (err) {
                return {
                    content: [{ type: "text", text: `Error: ${err}` }],
                    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 and successfully explains behavioral flags (spam filtering defaults to true, metadata exclusion for performance, uncached fetching for freshness). However, it omits mention of rate limits, authentication requirements, or pagination behavior for large wallets.

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?

The description follows a clear four-part structure: purpose, required params, optional params, and return value. While listing all parameters with defaults is slightly redundant given the schema, every sentence provides actionable information without filler.

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?

Given the 100% input schema coverage and lack of output schema, the description adequately covers inputs and provides a general statement about return values ('complete details... including metadata'). It could be improved by mentioning result pagination or typical response size limits for large collections.

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 organizes parameters into Required/Optional sections and repeats default values, but adds minimal semantic meaning beyond what the schema already documents (e.g., no additional guidance on valid ENS formats or address checksums).

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?

The description clearly states the tool 'render[s] the NFTs (including ERC721 and ERC1155) held by an address', providing specific verb (render), resource (NFTs), and scope (ERC721/ERC1155 standards). It distinguishes from siblings like nft_check_ownership by focusing on listing all holdings rather than verifying specific ownership.

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?

The phrase 'Commonly used to render...' provides implied usage context, but there is no explicit guidance on when to use this versus nft_check_ownership or nft_check_ownership_token_id, nor are there exclusion criteria or prerequisites 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/covalenthq/goldrush-mcp-server'

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