Skip to main content
Glama

fetchNftsOwnedByMultichainAddresses

Retrieve NFTs owned by wallet addresses across multiple blockchain networks, with configurable filters for spam and metadata inclusion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressesYesA list of wallet address and network pairs
withMetadataNoWhether to include metadata in the results.
pageKeyNoThe cursor to start the search from. Use this to paginate through the results.
pageSizeNoThe number of results to return. Default is 100. Max is 100

Implementation Reference

  • Core handler function that executes the API call to Alchemy's NFT endpoint to fetch NFTs owned by the given multichain addresses.
    async getNftsForAddress(params: NftsByAddressParams) {
      try {
        const client = createNftClient();
        
        const response = await client.post('/by-address', { 
          ...params
        });
    
        return response.data;
      } catch (error) {
        console.error('Error fetching NFTs for address:', error);
        throw error;
      }
    },
  • index.ts:253-283 (registration)
    Tool registration including Zod input schema validation and inline wrapper handler that calls the core alchemyApi handler and formats response.
    server.tool('fetchNftsOwnedByMultichainAddresses', {
      addresses: z.array(z.object({
        address: z.string().describe('The wallet address to query. e.g. "0x1234567890123456789012345678901234567890"'),
        networks: z.array(z.string()).default(['eth-mainnet']).describe('The blockchain networks to query. e.g. ["eth-mainnet", "base-mainnet"]'),
        excludeFilters: z.array(z.enum(['SPAM', 'AIRDROPS'])).default(["SPAM", "AIRDROPS"]).describe('The filters to exclude from the results. e.g. ["SPAM", "AIRDROPS"]'),
        includeFilters: z.array(z.enum(['SPAM', 'AIRDROPS'])).default([]).describe('The filters to include in the results. e.g. ["SPAM", "AIRDROPS"]'),
        spamConfidenceLevel: z.enum(['LOW', 'MEDIUM', 'HIGH', 'VERY_HIGH']).default('VERY_HIGH').describe('The spam confidence level to query. e.g. "LOW" or "HIGH"'),
      })).describe('A list of wallet address and network pairs'),
      withMetadata: z.boolean().default(true).describe('Whether to include metadata in the results.'),
      pageKey: z.string().optional().describe('The cursor to start the search from. Use this to paginate through the results.'),
      pageSize: z.number().default(10).describe('The number of results to return. Default is 100. Max is 100'),
    }, async (params) => {
      try {
        const result = await alchemyApi.getNftsForAddress(params);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      } catch (error) {
        if (error instanceof Error) {
          console.error('Error in getNFTsForOwner:', error);
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true
          };
        }
        return {
          content: [{ type: "text", text: 'Unknown error occurred' }],
          isError: true
        };
      }
    });
  • TypeScript type definitions for the input parameters of the NFT fetch tool, matching the Zod schema.
    export interface NftsByAddressParams {
      addresses: NftsByAddressPair[];
      withMetadata: boolean;
      pageKey?: string;
      pageSize: number;
    }
    
    export interface NftsByAddressPair {
      address: string;
      networks: string[];
      excludeFilters: Array<'SPAM' | 'AIRDROPS'>;
      includeFilters: Array<'SPAM' | 'AIRDROPS'>;
      spamConfidenceLevel: 'LOW' | 'MEDIUM' | 'HIGH' | 'VERY_HIGH';
    }
  • Helper function that creates the Axios HTTP client configured for Alchemy's NFT API endpoint.
    export const createNftClient = () => axios.create({
      baseURL: `https://api.g.alchemy.com/data/v1/${API_KEY}/assets/nfts`,
      headers: {
          'accept': 'application/json',
          'content-type': 'application/json',
          'x-alchemy-client-breadcrumb': BREADCRUMB_HEADER
      },
    });
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/alchemyplatform/alchemy-mcp-server'

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