Skip to main content
Glama
chainfetch

ChainFETCH MCP Server

Official
by chainfetch

search_blocks_json

Search Ethereum blockchain blocks using JSON queries with 120+ filterable parameters including hash, height range, gas usage, transaction count, and miner address.

Instructions

JSON search for blocks with 120+ parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashNoBlock hash
height_minNoMinimum block height
height_maxNoMaximum block height
gas_used_minNoMinimum gas used
gas_used_maxNoMaximum gas used
transaction_count_minNoMinimum transaction count
transaction_count_maxNoMaximum transaction count
miner_hashNoMiner address hash
limitNoNumber of results to return (default: 10, max: 50)
offsetNoNumber of results to skip for pagination (default: 0)

Implementation Reference

  • index.js:288-338 (registration)
    Registration of the search_blocks_json tool, including its description and input schema definition.
    {
      name: 'search_blocks_json',
      description: 'JSON search for blocks with 120+ parameters',
      inputSchema: {
        type: 'object',
        properties: {
          hash: {
            type: 'string',
            description: 'Block hash',
          },
          height_min: {
            type: 'integer',
            description: 'Minimum block height',
          },
          height_max: {
            type: 'integer',
            description: 'Maximum block height',
          },
          gas_used_min: {
            type: 'string',
            description: 'Minimum gas used',
          },
          gas_used_max: {
            type: 'string',
            description: 'Maximum gas used',
          },
          transaction_count_min: {
            type: 'integer',
            description: 'Minimum transaction count',
          },
          transaction_count_max: {
            type: 'integer',
            description: 'Maximum transaction count',
          },
          miner_hash: {
            type: 'string',
            description: 'Miner address hash',
          },
          limit: {
            type: 'integer',
            description: 'Number of results to return (default: 10, max: 50)',
            default: 10,
          },
          offset: {
            type: 'integer',
            description: 'Number of results to skip for pagination (default: 0)',
            default: 0,
          },
        },
        required: [],
      },
  • Handler case for search_blocks_json tool that delegates to the makeRequest helper to call the ChainFETCH API endpoint.
    case 'search_blocks_json':
      return await this.makeRequest('/api/v1/ethereum/blocks/json_search', 'GET', args, null, token);
  • Shared helper function makeRequest used by all tools, including search_blocks_json, to make authenticated API requests to ChainFETCH endpoints.
    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();
    }
Behavior1/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. The description fails to disclose any behavioral traits such as read/write nature, rate limits, authentication needs, or what the search returns (e.g., JSON structure, pagination details). The mention of '120+ parameters' is misleading as the input schema only lists 10 parameters, creating confusion rather than transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence but is not front-loaded with useful information. It wastes space on the misleading '120+ parameters' claim instead of stating the tool's purpose clearly. While concise in length, it lacks effective structure and fails to convey essential details efficiently.

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 a search tool with 10 parameters, no annotations, and no output schema, the description is incomplete. It does not explain the search behavior, return format, or how parameters interact (e.g., filtering logic). The inaccuracy about parameter count further undermines completeness, leaving significant gaps for the agent to understand tool 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?

Schema description coverage is 100%, so the schema already documents all 10 parameters thoroughly. The description adds no meaningful semantic information beyond what's in the schema. The mention of '120+ parameters' is inaccurate and does not compensate for or clarify the actual parameters. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'JSON search for blocks with 120+ parameters' is vague and tautological. It restates the tool name ('search_blocks_json') without specifying the action verb or resource clearly. While 'search' is implied, it doesn't distinguish this tool from sibling search tools like 'search_blocks_llm' or 'search_blocks_semantic' beyond the 'JSON' format mention, which is insufficient for differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions. Given the many sibling tools (e.g., 'search_blocks_llm', 'search_blocks_semantic', 'get_block_info'), the lack of usage guidelines leaves the agent without direction on tool selection.

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