Skip to main content
Glama

get_nft_metadata

Retrieve detailed NFT metadata including name, image, and attributes using contract addresses and token IDs for EVM chains or mint addresses for Solana.

Instructions

Get detailed metadata for a specific NFT (name, image, attributes, CAIP-19 assetId). EVM: contractAddress:tokenId, Solana: mintAddress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
token_identifierYesNFT identifier. EVM: {contractAddress}:{tokenId}. Solana: {mintAddress}.
networkYesNetwork identifier (e.g., "ethereum-mainnet", "solana-mainnet" or CAIP-2 "eip155:1").
wallet_idNoTarget wallet ID. Required for multi-wallet sessions.

Implementation Reference

  • Handler implementation for get_nft_metadata tool which calls the API client to fetch NFT metadata.
    async (args) => {
      const params = new URLSearchParams();
      params.set('network', args.network);
      if (args.wallet_id) params.set('walletId', args.wallet_id);
      const result = await apiClient.get(
        `/v1/wallet/nfts/${encodeURIComponent(args.token_identifier)}?${params.toString()}`,
      );
      return toToolResult(result);
    },
  • Tool registration function for get_nft_metadata.
    export function registerGetNftMetadata(
      server: McpServer,
      apiClient: ApiClient,
      walletContext?: WalletContext,
    ): void {
      server.tool(
        'get_nft_metadata',
        withWalletPrefix(
          'Get detailed metadata for a specific NFT (name, image, attributes, CAIP-19 assetId). EVM: contractAddress:tokenId, Solana: mintAddress.',
          walletContext?.walletName,
        ),
        {
          token_identifier: z.string().describe('NFT identifier. EVM: {contractAddress}:{tokenId}. Solana: {mintAddress}.'),
          network: z.string().describe('Network identifier (e.g., "ethereum-mainnet", "solana-mainnet" or CAIP-2 "eip155:1").'),
          wallet_id: z.string().optional().describe('Target wallet ID. Required for multi-wallet sessions.'),
        },
        async (args) => {
          const params = new URLSearchParams();
          params.set('network', args.network);
          if (args.wallet_id) params.set('walletId', args.wallet_id);
          const result = await apiClient.get(
            `/v1/wallet/nfts/${encodeURIComponent(args.token_identifier)}?${params.toString()}`,
          );
          return toToolResult(result);
        },
      );
    }
Behavior4/5

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

No annotations provided, so description carries full burden. Successfully discloses return values (name, image, attributes, CAIP-19 assetId) and blockchain format standards. Missing operational details like rate limits or caching behavior, but CAIP-19 mention adds valuable standard context.

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?

Single dense sentence with zero waste. Front-loaded action verb, parenthetical return value list, and format examples. Every clause earns its place.

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?

Appropriate for a 3-parameter read tool without output schema. Covers identifier formats and return fields well. Could mention read-only nature or error cases (e.g., 'not found'), but sufficient for tool selection.

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 has 100% description coverage, establishing baseline 3. Description repeats the EVM/Solana format examples already in schema, adding minimal new semantic value for parameters specifically, though CAIP-19 reference provides standard context.

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?

Clear specific verb 'Get' with resource 'NFT metadata'. Explicitly distinguishes from sibling 'list_nfts' by focusing on a 'specific NFT' and 'detailed' metadata, and from 'transfer_nft' by being a read operation.

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 format examples for EVM vs Solana chains, implicitly guiding correct usage. However, lacks explicit guidance on when to use this vs 'list_nfts' (detailed lookup vs enumeration) or when 'wallet_id' is required (though schema covers this).

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/minhoyoo-iotrust/WAIaaS'

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