Skip to main content
Glama
chainfetch

ChainFETCH MCP Server

Official
by chainfetch

get_smart_contract_info

Retrieve detailed information about a specific smart contract by providing its address, enabling analysis of contract data and functionality.

Instructions

Get detailed information about a specific smart contract

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe smart contract address

Implementation Reference

  • index.js:594-607 (registration)
    Registration of the 'get_smart_contract_info' tool including its input schema, description, and required 'address' parameter.
    {
      name: 'get_smart_contract_info',
      description: 'Get detailed information about a specific smart contract',
      inputSchema: {
        type: 'object',
        properties: {
          address: {
            type: 'string',
            description: 'The smart contract address',
          },
        },
        required: ['address'],
      },
    },
  • Handler function for 'get_smart_contract_info': extracts contract address from arguments and proxies the request to the ChainFetch API endpoint for smart contract details.
    case 'get_smart_contract_info':
      const { address: contractAddress } = args;
      return await this.makeRequest(`/api/v1/ethereum/smart-contracts/${contractAddress}`, 'GET', {}, null, token);
  • Shared helper method that performs authenticated HTTP requests to the ChainFetch API, used by all tool handlers including get_smart_contract_info.
    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 of behavioral disclosure. While 'Get' implies a read operation, the description doesn't address important behavioral aspects: whether this requires authentication, rate limits, what format the 'detailed information' returns, error conditions, or whether it's a real-time query versus cached data. For a tool with no annotation coverage, this leaves significant 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 gets straight to the point with no wasted words. It's appropriately sized for a simple tool with one parameter and follows good front-loading by immediately stating the core function.

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 should do more to compensate. For a tool that presumably returns complex smart contract data, the description doesn't indicate what 'detailed information' includes, the response format, or any behavioral constraints. With no structured output documentation and multiple similar sibling tools, this leaves the agent with insufficient context for optimal tool selection and 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 has 100% description coverage with the 'address' parameter clearly documented as 'The smart contract address'. The description doesn't add any additional parameter semantics beyond what the schema provides - it doesn't clarify address format requirements, validation rules, or examples. With complete schema coverage, the baseline score of 3 is appropriate.

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 verb ('Get') and resource ('detailed information about a specific smart contract'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'get_smart_contract_summary' - both appear to retrieve smart contract information, so the differentiation between 'detailed information' and 'summary' is implied but not explicit.

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 about when to use this tool versus alternatives. With multiple sibling tools for smart contracts (get_smart_contract_summary, search_smart_contracts_json/llm/semantic), there's no indication of when 'detailed information' is preferred over a 'summary' or when to use search tools instead. The description only states what it does, not when to choose it.

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