Skip to main content
Glama
chainfetch

ChainFETCH MCP Server

Official
by chainfetch

get_token_summary

Generate AI-powered summaries for Ethereum tokens by providing their address, enabling quick understanding of token details and characteristics.

Instructions

Get AI-generated summary for a specific token

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
token_addressYesThe token address hash to get summary for

Implementation Reference

  • index.js:460-473 (registration)
    Registration of the 'get_token_summary' tool in the ListTools response, defining its name, description, and input schema (requires 'token_address').
    {
      name: 'get_token_summary',
      description: 'Get AI-generated summary for a specific token',
      inputSchema: {
        type: 'object',
        properties: {
          token_address: {
            type: 'string',
            description: 'The token address hash to get summary for',
          },
        },
        required: ['token_address'],
      },
    },
  • The handler logic for executing the 'get_token_summary' tool: calls makeRequest to proxy the arguments to the ChainFETCH API endpoint '/api/v1/ethereum/tokens/summary'.
    case 'get_token_summary':
      return await this.makeRequest('/api/v1/ethereum/tokens/summary', 'GET', args, null, token);
  • Shared helper method 'makeRequest' that performs authenticated HTTP requests to the ChainFETCH API, used by the get_token_summary handler and all other tools.
    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 but discloses minimal behavioral traits. It mentions the output is 'AI-generated', which adds some context about the nature of the summary, but lacks details on permissions, rate limits, response format, or potential errors. This is inadequate for a tool with no annotation coverage.

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 directly states the tool's function without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 incomplete. It doesn't explain what the summary contains, how it's formatted, or any limitations (e.g., token types supported). For a tool with no structured output documentation, this leaves significant gaps for an agent to understand the tool's behavior.

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 description adds no meaning beyond the input schema, which has 100% coverage for the single parameter 'token_address'. The schema's description already explains it as 'The token address hash to get summary for', so the tool description provides no additional parameter context, meeting the baseline for high schema coverage.

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 states the tool retrieves an AI-generated summary for a token, which is a clear purpose but lacks specificity. It doesn't distinguish from sibling tools like 'get_token_info' or 'get_address_summary', leaving ambiguity about what makes this summary unique or how it differs from other summary tools.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools available (e.g., get_token_info, search_tokens_llm), the description offers no context, prerequisites, or exclusions, leaving the agent to guess based on the name alone.

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