Skip to main content
Glama
chainfetch

ChainFETCH MCP Server

Official
by chainfetch

get_block_info

Retrieve detailed information about a specific Ethereum block by providing its block number to analyze blockchain data.

Instructions

Get detailed information about a specific block

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blockYesThe block number to get info for

Implementation Reference

  • index.js:368-381 (registration)
    Registration of the 'get_block_info' tool in the ListTools response, including name, description, and input schema.
    {
      name: 'get_block_info',
      description: 'Get detailed information about a specific block',
      inputSchema: {
        type: 'object',
        properties: {
          block: {
            type: 'string',
            description: 'The block number to get info for',
          },
        },
        required: ['block'],
      },
    },
  • Input schema definition for the 'get_block_info' tool, specifying the required 'block' parameter as a string.
    inputSchema: {
      type: 'object',
      properties: {
        block: {
          type: 'string',
          description: 'The block number to get info for',
        },
      },
      required: ['block'],
    },
  • Handler implementation for 'get_block_info' tool. Extracts the block number from arguments and forwards the request to the ChainFETCH API endpoint /api/v1/ethereum/blocks/{block}.
    case 'get_block_info':
      const { block } = args;
      return await this.makeRequest(`/api/v1/ethereum/blocks/${block}`, 'GET', {}, null, token);
  • Helper method 'makeRequest' used by the 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. While 'Get' implies a read operation, the description doesn't address important behavioral aspects like whether this requires authentication, rate limits, what format the detailed information returns, or potential error conditions for invalid block numbers.

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 extremely concise - a single sentence that directly states the tool's purpose. There's no wasted language or unnecessary elaboration, making it easy to parse and understand 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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'detailed information' includes, how it differs from 'get_block_summary', what format the response takes, or any behavioral constraints. Given the complexity implied by sibling tools and lack of structured metadata, more context is needed.

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 single parameter 'block' clearly documented as 'The block number to get info for'. The description doesn't add any additional parameter semantics beyond what's already in the schema, so 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 block'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'get_block_summary' - both appear to retrieve block information but with different detail levels.

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 sibling tools like 'get_block_summary' and multiple search tools for blocks, there's no indication of when detailed block information is needed versus summary information or search functionality.

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