Skip to main content
Glama
chainfetch

ChainFETCH MCP Server

Official
by chainfetch

get_token_info

Retrieve detailed blockchain information for a specific token address, including contract data, metadata, and on-chain activity.

Instructions

Get detailed information about a specific token

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesThe token address hash

Implementation Reference

  • Handler for 'get_token_info' tool: extracts token address from args and calls makeRequest to fetch token info from ChainFETCH API endpoint /api/v1/ethereum/tokens/{tokenAddress}
    case 'get_token_info':
      const { token: tokenAddress } = args;
      return await this.makeRequest(`/api/v1/ethereum/tokens/${tokenAddress}`, 'GET', {}, null, token);
  • Input schema for get_token_info tool: requires a 'token' string parameter (token address hash)
    inputSchema: {
      type: 'object',
      properties: {
        token: {
          type: 'string',
          description: 'The token address hash',
        },
      },
      required: ['token'],
    },
  • index.js:474-487 (registration)
    Registration of 'get_token_info' tool in the list returned by ListToolsRequestSchema handler, including name, description, and input schema
    {
      name: 'get_token_info',
      description: 'Get detailed information about a specific token',
      inputSchema: {
        type: 'object',
        properties: {
          token: {
            type: 'string',
            description: 'The token address hash',
          },
        },
        required: ['token'],
      },
    },
  • Helper method used by the handler to make authenticated HTTP requests to the ChainFETCH API using node-fetch, handling query params, auth token, and error handling
    async makeRequest(endpoint, method = 'GET', params = {}, body = null, token = null) {
      const chainfetchToken = token || process.env.CHAINFETCH_API_TOKEN;
      
      if (!chainfetchToken) {
        throw new McpError(
          ErrorCode.InvalidRequest,
          'CHAINFETCH_API_TOKEN is required'
        );
      }
    
      const url = new URL(`${API_BASE_URL}${endpoint}`);
      
      // Add query parameters for GET requests
      if (method === 'GET' && Object.keys(params).length > 0) {
        Object.entries(params).forEach(([key, value]) => {
          if (value !== undefined && value !== null) {
            if (Array.isArray(value)) {
              value.forEach(v => url.searchParams.append(`${key}[]`, v));
            } else {
              url.searchParams.append(key, value.toString());
            }
          }
        });
      }
    
      const fetchOptions = {
        method,
        headers: {
          'Authorization': `Bearer ${chainfetchToken}`,
          'Content-Type': 'application/json',
        },
      };
    
      if (body && method !== 'GET') {
        fetchOptions.body = JSON.stringify(body);
      }
    
      const response = await fetch(url.toString(), fetchOptions);
      
      if (!response.ok) {
        const errorText = await response.text();
        throw new McpError(
          ErrorCode.InternalError,
          `API request failed: ${response.status} ${response.statusText} - ${errorText}`
        );
      }
    
      return await response.json();
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get detailed information' implies a read-only operation, it doesn't specify what constitutes 'detailed information', whether there are rate limits, authentication requirements, or what format the information returns. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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?

The description is a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple lookup tool and front-loads the essential information.

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 lack of annotations and output schema, the description is insufficiently complete. For a tool that presumably returns structured token data, the description doesn't hint at what information is included, whether there are common use cases, or how this differs from the summary version. The context signals show this is a simple single-parameter tool, but the description doesn't provide enough guidance for optimal agent usage.

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?

The schema description coverage is 100% with the single parameter 'token' clearly documented as 'The token address hash'. The description adds no additional parameter semantics beyond what's already in the schema. With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't need to.

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

Purpose4/5

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

The description clearly states the action ('Get detailed information') and target resource ('about a specific token'), making the purpose immediately understandable. It distinguishes from summary tools like 'get_token_summary' by specifying 'detailed information', but doesn't explicitly contrast with other token-related tools like 'search_tokens_json' or 'get_nft_instance_info'.

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 multiple sibling tools including 'get_token_summary' and various search tools, there's no indication of when detailed token information is preferred over summaries or search results, nor any mention of prerequisites or constraints.

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