Skip to main content
Glama
chainfetch

ChainFETCH MCP Server

Official
by chainfetch

get_address_info

Retrieve detailed Ethereum address information including transaction history, token holdings, and smart contract data for blockchain analysis and verification.

Instructions

Get detailed information about a specific Ethereum address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe address hash to get info for

Implementation Reference

  • The handler function for the 'get_address_info' tool. It extracts the address from arguments and makes an API GET request to the ChainFETCH API endpoint for that specific address.
    case 'get_address_info':
      const { address } = args;
      return await this.makeRequest(`/api/v1/ethereum/addresses/${address}`, 'GET', {}, null, token);
  • Input schema definition for the 'get_address_info' tool, specifying the required 'address' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        address: {
          type: 'string',
          description: 'The address hash to get info for',
        },
      },
      required: ['address'],
    },
  • index.js:136-149 (registration)
    Registration of the 'get_address_info' tool in the listTools response, including name, description, and input schema.
    {
      name: 'get_address_info',
      description: 'Get detailed information about a specific Ethereum address',
      inputSchema: {
        type: 'object',
        properties: {
          address: {
            type: 'string',
            description: 'The address hash to get info for',
          },
        },
        required: ['address'],
      },
    },
  • Helper method 'makeRequest' used by the tool handler to perform authenticated HTTP requests to the ChainFETCH API.
    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. It mentions 'detailed information' but doesn't specify what that includes (e.g., balance, transaction history, contract interactions), nor does it cover aspects like rate limits, authentication needs, or error handling, leaving significant gaps for a tool with no structured safety hints.

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 is appropriately sized and front-loaded, with every part contributing essential information, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (single parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on return values, error cases, or behavioral traits, which are needed for full contextual understanding, especially with no output schema to compensate.

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 100% description coverage, with the single parameter 'address' documented as 'The address hash to get info for'. The description adds no additional meaning beyond this, such as format requirements (e.g., checksum, prefix) or examples, so it meets the baseline for high schema coverage without compensating further.

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 Ethereum address'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'get_address_summary' or 'get_address_info' alternatives, which would require specifying what 'detailed information' entails compared to a summary.

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 like 'get_address_summary' and various search tools, it lacks explicit when-to-use or when-not-to-use instructions, leaving usage context implied at best.

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