Skip to main content
Glama
chainfetch

ChainFETCH MCP Server

Official
by chainfetch

search_tokens_llm

Use AI to search for tokens by describing what you need in natural language. This tool analyzes your query to select optimal search parameters for finding relevant tokens on the Ethereum blockchain.

Instructions

LLM-powered token search using AI to select optimal parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language query for token search

Implementation Reference

  • index.js:447-459 (registration)
    Registration of the 'search_tokens_llm' tool including name, description, and input schema requiring a 'query' parameter.
      name: 'search_tokens_llm',
      description: 'LLM-powered token search using AI to select optimal parameters',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Natural language query for token search',
          },
        },
        required: ['query'],
      },
    },
  • Input schema for search_tokens_llm tool: object with required 'query' string.
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'Natural language query for token search',
        },
      },
      required: ['query'],
    },
  • Handler implementation: proxies the call to ChainFETCH API endpoint '/api/v1/ethereum/tokens/llm_search' using makeRequest method with GET and provided args.
    case 'search_tokens_llm':
      return await this.makeRequest('/api/v1/ethereum/tokens/llm_search', 'GET', args, null, token);
  • Shared helper method that makes authenticated HTTP requests to the ChainFETCH API base URL, handles query params, auth token, and error handling. Used by all tool handlers including search_tokens_llm.
    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 the full burden. It mentions 'LLM-powered' and 'AI to select optimal parameters', which hints at AI-based processing, but doesn't disclose critical behavioral traits such as rate limits, authentication needs, error handling, or what 'optimal parameters' entails. This leaves significant gaps for an AI agent to understand how to invoke it effectively.

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 that front-loads key information ('LLM-powered token search'). It avoids redundancy and waste, though it could be slightly more structured by separating purpose from method. Overall, it's appropriately sized for a simple tool.

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 tool's complexity (AI-powered search with no output schema and no annotations), the description is incomplete. It lacks details on output format, error cases, performance expectations, and how it differs behaviorally from sibling tools. Without annotations or output schema, the description should provide more context to guide effective 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?

The input schema has 1 parameter with 100% description coverage, providing a clear description ('Natural language query for token search'). The description adds minimal value beyond the schema by implying the query is processed with AI, but doesn't elaborate on format, examples, or constraints. With high schema coverage, the baseline is 3, as the description doesn't significantly enhance parameter understanding.

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 performs 'LLM-powered token search' which indicates the verb (search) and resource (tokens), but it's vague about what 'token search' means in this context (e.g., searching token metadata, transactions, holders). It distinguishes from siblings by mentioning 'LLM-powered' and 'AI to select optimal parameters', but doesn't clearly differentiate from other token search tools like 'search_tokens_json' or 'search_tokens_semantic' beyond the AI aspect.

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 explicit guidance on when to use this tool versus alternatives. It mentions 'LLM-powered' and 'AI to select optimal parameters', which implies usage for natural language queries, but doesn't specify scenarios, prerequisites, or exclusions compared to other token search tools like 'search_tokens_json' or 'search_tokens_semantic'.

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