Skip to main content
Glama
chainfetch

ChainFETCH MCP Server

Official
by chainfetch

search_transactions_json

Search Ethereum blockchain transactions using 254+ parameters like hash, value, gas usage, addresses, and block numbers to filter and retrieve specific transaction data.

Instructions

JSON search for transactions with 254+ carefully curated parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashNoTransaction hash
value_minNoMinimum transaction value in WEI
value_maxNoMaximum transaction value in WEI
gas_used_minNoMinimum gas used
gas_used_maxNoMaximum gas used
from_hashNoFrom address hash
to_hashNoTo address hash
block_number_minNoMinimum block number
block_number_maxNoMaximum block number
limitNoNumber of results to return (default: 10, max: 50)
offsetNoNumber of results to skip for pagination (default: 0)

Implementation Reference

  • The handler case for 'search_transactions_json' tool that executes the tool logic by calling makeRequest to the ChainFETCH API endpoint '/api/v1/ethereum/transactions/json_search'.
    case 'search_transactions_json':
      return await this.makeRequest('/api/v1/ethereum/transactions/json_search', 'GET', args, null, token);
  • index.js:170-225 (registration)
    Registration of the 'search_transactions_json' tool in the ListTools response, including its name, description, and input schema.
    {
      name: 'search_transactions_json',
      description: 'JSON search for transactions with 254+ carefully curated parameters',
      inputSchema: {
        type: 'object',
        properties: {
          hash: {
            type: 'string',
            description: 'Transaction hash',
          },
          value_min: {
            type: 'string',
            description: 'Minimum transaction value in WEI',
          },
          value_max: {
            type: 'string',
            description: 'Maximum transaction value in WEI',
          },
          gas_used_min: {
            type: 'string',
            description: 'Minimum gas used',
          },
          gas_used_max: {
            type: 'string',
            description: 'Maximum gas used',
          },
          from_hash: {
            type: 'string',
            description: 'From address hash',
          },
          to_hash: {
            type: 'string',
            description: 'To address hash',
          },
          block_number_min: {
            type: 'integer',
            description: 'Minimum block number',
          },
          block_number_max: {
            type: 'integer',
            description: 'Maximum block number',
          },
          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: [],
      },
    },
  • Input schema definition for the 'search_transactions_json' tool, defining parameters for JSON-based transaction search.
    inputSchema: {
      type: 'object',
      properties: {
        hash: {
          type: 'string',
          description: 'Transaction hash',
        },
        value_min: {
          type: 'string',
          description: 'Minimum transaction value in WEI',
        },
        value_max: {
          type: 'string',
          description: 'Maximum transaction value in WEI',
        },
        gas_used_min: {
          type: 'string',
          description: 'Minimum gas used',
        },
        gas_used_max: {
          type: 'string',
          description: 'Maximum gas used',
        },
        from_hash: {
          type: 'string',
          description: 'From address hash',
        },
        to_hash: {
          type: 'string',
          description: 'To address hash',
        },
        block_number_min: {
          type: 'integer',
          description: 'Minimum block number',
        },
        block_number_max: {
          type: 'integer',
          description: 'Maximum block number',
        },
        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: [],
    },
  • Helper function 'makeRequest' that performs HTTP requests to the ChainFETCH API, used by all tool handlers including search_transactions_json.
    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 full burden. It mentions 'JSON search' and '254+ carefully curated parameters', which hints at a structured, parameter-rich search, but doesn't disclose critical behavioral traits like whether this is a read-only operation, performance characteristics, rate limits, authentication needs, or what the output format looks like. For a search tool with zero annotation coverage, this is inadequate.

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

Conciseness4/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 without unnecessary words. It could be slightly improved by front-loading more critical information, but it's appropriately sized for its purpose.

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 (11 parameters, no annotations, no output schema), the description is insufficient. It doesn't explain the return format (only mentions 'JSON search' vaguely), doesn't clarify the relationship between the 11 shown parameters and the '254+ curated parameters', and provides no behavioral context. For a search tool with rich parameters, this leaves significant gaps.

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 11 parameters thoroughly. The description adds minimal value by mentioning '254+ carefully curated parameters' (implying many more than the 11 shown), but doesn't provide specifics about those additional parameters or how to access them. Baseline 3 is appropriate when the schema does the heavy lifting.

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 tool performs 'JSON search for transactions' with a specific scope of '254+ carefully curated parameters', which is a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from its siblings (search_transactions_llm, search_transactions_semantic) beyond the 'JSON' format mention, which is why it doesn't reach a 5.

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 search_transactions_llm or search_transactions_semantic. It mentions '254+ carefully curated parameters' which might imply this is for detailed filtering, but this is not explicit usage guidance. No exclusions or prerequisites are stated.

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