Skip to main content
Glama

getNFTTokenURI

Retrieve the token URI for an ERC721 NFT by providing the contract address and token ID. This tool enables access to NFT metadata stored on-chain through the MCP Ethers Wallet server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contractAddressYesThe address of the ERC721 contract
tokenIdYesThe ID of the token to get the URI for
providerNoOptional. The provider to use. If not provided, the default provider is used.
chainIdNoOptional. The chain ID to use.

Implementation Reference

  • The core handler logic for the 'getNFTTokenURI' tool. It uses the EthersService to fetch ERC721 metadata for the given contract and token ID, extracts the token URI, and returns it in the MCP response format. Handles errors gracefully.
    async (params) => {
      try {
        // Get the metadata which includes the token URI
        const metadata = await ethersService.getERC721Metadata(
          params.contractAddress,
          params.tokenId,
          params.provider,
          params.chainId
        );
        
        const uri = metadata.uri || "";
        
        return {
          content: [{ 
            type: "text", 
            text: `Token URI for token ${params.tokenId} is ${uri}`
          }]
        };
      } catch (error) {
        return {
          isError: true,
          content: [{ 
            type: "text", 
            text: `Error getting NFT token URI: ${error instanceof Error ? error.message : String(error)}`
          }]
        };
      }
    }
  • TypeScript type definition for the input parameters of the getNFTTokenURI tool.
    type GetNFTTokenURIParams = {
      contractAddress: string;
      tokenId: string | number;
      provider?: string;
      chainId?: number;
    };
  • Zod-based input schema for validating parameters in the getNFTTokenURI tool registration.
    {
      contractAddress: contractAddressSchema.describe("The address of the ERC721 contract"),
      tokenId: tokenIdSchema.describe("The ID of the token to get the URI for"),
      provider: providerSchema.describe("Optional. The provider to use. If not provided, the default provider is used."),
      chainId: chainIdSchema.describe("Optional. The chain ID to use.")
    },
  • Direct registration of the getNFTTokenURI tool with the MCP server via server.tool(), including schema and handler.
    server.tool(
      "getNFTTokenURI",
      {
        contractAddress: contractAddressSchema.describe("The address of the ERC721 contract"),
        tokenId: tokenIdSchema.describe("The ID of the token to get the URI for"),
        provider: providerSchema.describe("Optional. The provider to use. If not provided, the default provider is used."),
        chainId: chainIdSchema.describe("Optional. The chain ID to use.")
      },
      async (params) => {
        try {
          // Get the metadata which includes the token URI
          const metadata = await ethersService.getERC721Metadata(
            params.contractAddress,
            params.tokenId,
            params.provider,
            params.chainId
          );
          
          const uri = metadata.uri || "";
          
          return {
            content: [{ 
              type: "text", 
              text: `Token URI for token ${params.tokenId} is ${uri}`
            }]
          };
        } catch (error) {
          return {
            isError: true,
            content: [{ 
              type: "text", 
              text: `Error getting NFT token URI: ${error instanceof Error ? error.message : String(error)}`
            }]
          };
        }
      }
    );
  • Invocation of registerERC721Tools in the main tools index, which registers the getNFTTokenURI tool among other ERC721 tools.
    registerERC721Tools(server, ethersService);
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/crazyrabbitLTC/mcp-ethers-server'

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