Skip to main content
Glama
chainfetch

ChainFETCH MCP Server

Official
by chainfetch

get_transaction_info

Retrieve detailed blockchain transaction data including sender, receiver, amount, and status for analysis and verification purposes.

Instructions

Get detailed information about a specific transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transactionYesThe transaction hash to get info for

Implementation Reference

  • Handler logic for the get_transaction_info tool: extracts the transaction hash from arguments and calls the makeRequest method to fetch data from the ChainFETCH API endpoint /api/v1/ethereum/transactions/{transaction}
    case 'get_transaction_info':
      const { transaction } = args;
      return await this.makeRequest(`/api/v1/ethereum/transactions/${transaction}`, 'GET', {}, null, token);
  • index.js:254-267 (registration)
    Registration of the get_transaction_info tool in the MCP server's tool list, defining its name, description, and input schema requiring a 'transaction' string parameter
    {
      name: 'get_transaction_info',
      description: 'Get detailed information about a specific transaction',
      inputSchema: {
        type: 'object',
        properties: {
          transaction: {
            type: 'string',
            description: 'The transaction hash to get info for',
          },
        },
        required: ['transaction'],
      },
    },
  • Input schema definition for get_transaction_info tool, specifying an object with a required 'transaction' string property
    inputSchema: {
      type: 'object',
      properties: {
        transaction: {
          type: 'string',
          description: 'The transaction hash to get info for',
        },
      },
      required: ['transaction'],
  • Shared helper method makeRequest used by get_transaction_info (and other tools) to make authenticated HTTP requests to the ChainFETCH API, handling token, parameters, and errors
    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 states it 'gets' information, implying a read-only operation, but doesn't mention any behavioral traits like rate limits, authentication requirements, error conditions, or what 'detailed information' entails (e.g., format, fields included). This leaves significant gaps for an agent to understand how to use it effectively.

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, clear sentence that efficiently conveys the core purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse 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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'detailed information' includes (e.g., fields, structure), how results are returned, or any operational constraints. For a tool with no structured output definition, this leaves the agent with insufficient context to handle the response effectively.

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 description adds no parameter information beyond what's already in the schema, which has 100% coverage for the single parameter 'transaction' (described as 'The transaction hash to get info for'). Since schema coverage is high, the baseline is 3, and the description doesn't compensate with additional context like hash format examples or validation rules.

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 transaction'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_transaction_summary' or 'search_transactions_json', leaving ambiguity about when to choose this specific tool over alternatives.

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 many sibling tools available (e.g., get_transaction_summary, search_transactions_json), there's no indication of when this detailed info tool is preferred over summary or search tools, or what distinguishes it from them.

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