Skip to main content
Glama
chainfetch

ChainFETCH MCP Server

Official
by chainfetch

get_nft_instance_info

Retrieve detailed information about a specific NFT instance using its token address and instance ID for blockchain analysis.

Instructions

Get NFT instance information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesThe token address
instance_idYesThe instance ID

Implementation Reference

  • The switch case handler that executes the get_nft_instance_info tool by extracting parameters and making an API request to the ChainFetch endpoint for the specific NFT token instance.
    case 'get_nft_instance_info':
      const { token: nftToken, instance_id } = args;
      return await this.makeRequest(`/api/v1/ethereum/token-instances/${nftToken}/${instance_id}`, 'GET', {}, null, token);
  • index.js:488-505 (registration)
    Tool registration in the listTools response, defining the name, description, and input schema for get_nft_instance_info.
    {
      name: 'get_nft_instance_info',
      description: 'Get NFT instance information',
      inputSchema: {
        type: 'object',
        properties: {
          token: {
            type: 'string',
            description: 'The token address',
          },
          instance_id: {
            type: 'string',
            description: 'The instance ID',
          },
        },
        required: ['token', 'instance_id'],
      },
    },
  • Input schema definition for the get_nft_instance_info tool, specifying required parameters token and instance_id.
    inputSchema: {
      type: 'object',
      properties: {
        token: {
          type: 'string',
          description: 'The token address',
        },
        instance_id: {
          type: 'string',
          description: 'The instance ID',
        },
      },
      required: ['token', 'instance_id'],
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but it doesn't specify whether this requires authentication, has rate limits, returns paginated results, or what the output format is. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 is a single, efficient sentence with no wasted words. It's front-loaded with the core purpose. However, given the lack of detail and sibling context, it could be argued it's under-specified rather than concise, but it meets the criteria for conciseness.

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

Completeness2/5

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

Given the complexity (2 required parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what 'NFT instance information' entails, how it differs from general token info, or what the return values might be. With no output schema and minimal behavioral context, this is inadequate for effective tool use.

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%, with both parameters (token and instance_id) documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., no examples, format details, or constraints). Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Get NFT instance information' clearly states the action (get) and resource (NFT instance information), which is adequate. However, it doesn't distinguish this tool from its many siblings (like get_token_info, get_smart_contract_info, etc.) by specifying what makes NFT instance information unique. The purpose is clear but lacks sibling differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With numerous sibling tools (e.g., get_token_info, search_tokens_json), there's no indication of context, prerequisites, or exclusions. This leaves the agent to infer usage based on the tool name alone, which is insufficient.

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

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