Skip to main content
Glama
chainfetch

ChainFETCH MCP Server

Official
by chainfetch

get_smart_contract_summary

Generate AI-powered summaries for Ethereum smart contracts by providing a contract address to understand contract functionality and purpose.

Instructions

Get AI-generated summary for a specific smart contract

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe smart contract address to get summary for

Implementation Reference

  • index.js:580-593 (registration)
    Registration of the 'get_smart_contract_summary' tool in the listTools response, including name, description, and input schema.
    {
      name: 'get_smart_contract_summary',
      description: 'Get AI-generated summary for a specific smart contract',
      inputSchema: {
        type: 'object',
        properties: {
          address: {
            type: 'string',
            description: 'The smart contract address to get summary for',
          },
        },
        required: ['address'],
      },
    },
  • Input schema for the get_smart_contract_summary tool, requiring a 'address' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        address: {
          type: 'string',
          description: 'The smart contract address to get summary for',
        },
      },
      required: ['address'],
    },
  • Handler logic for get_smart_contract_summary: proxies the request parameters to the ChainFetch API endpoint '/api/v1/ethereum/smart-contracts/summary'.
    case 'get_smart_contract_summary':
      return await this.makeRequest('/api/v1/ethereum/smart-contracts/summary', 'GET', args, null, token);
  • Helper method makeRequest used by all tools, including get_smart_contract_summary, to make authenticated API calls to ChainFetch with proper parameter handling and error management.
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'AI-generated summary' but doesn't specify what that entails (e.g., content, length, reliability), whether it's read-only, or if there are rate limits or authentication needs. This leaves significant gaps in understanding the tool's behavior.

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 purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to grasp 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 complexity of smart contract analysis and the lack of annotations and output schema, the description is incomplete. It doesn't explain what the summary includes, how it's generated, or what the output looks like, which are critical for an AI agent to use this tool effectively.

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 parameter 'address' well-documented in the schema. The description doesn't add any extra meaning beyond what the schema provides, such as address format examples or constraints, so it meets the baseline for high coverage without compensation.

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 AI-generated summary') and resource ('for a specific smart contract'), making the purpose understandable. However, it doesn't explicitly distinguish this tool from its sibling 'get_smart_contract_info' or other summary tools, which would be needed for a perfect score.

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 like 'get_smart_contract_info' or other summary tools in the sibling list. It lacks context about prerequisites, such as whether the address must be verified or what format it expects, leaving usage unclear.

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