Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

get_transaction_receipt

Retrieve transaction receipts on Arbitrum networks using transaction hashes to verify execution status and details.

Instructions

Get transaction receipt by hash

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rpcUrlNoThe RPC URL of the chain (optional if default is set)
txHashYesTransaction hash

Implementation Reference

  • Handler logic for the get_transaction_receipt MCP tool. Resolves RPC URL from args or chainName, creates EthereumAccountClient instance, fetches transaction receipt using the client's method, and returns JSON stringified response.
    case "get_transaction_receipt": {
      const rpcUrl = await this.resolveRpcUrl(
        (args.rpcUrl as string) || (args.chainName as string)
      );
      const ethereumAccountClient = new EthereumAccountClient(rpcUrl);
      const receipt = await ethereumAccountClient.getTransactionReceipt(
        args.txHash as string
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(receipt, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the get_transaction_receipt tool returned by list tools handler. Defines required txHash and optional rpcUrl parameters.
      name: "get_transaction_receipt",
      description: "Get transaction receipt by hash",
      inputSchema: {
        type: "object" as const,
        properties: {
          rpcUrl: {
            type: "string",
            description:
              "The RPC URL of the chain (optional if default is set)",
          },
          txHash: {
            type: "string",
            description: "Transaction hash",
          },
        },
        required: ["txHash"],
      },
    },
  • Core implementation of transaction receipt fetching via eth_getTransactionReceipt RPC call, with response parsing to Receipt type. Called by the MCP tool handler.
    async getTransactionReceipt(txHash: string): Promise<Receipt> {
      const receipt = await this.makeRpcCall('eth_getTransactionReceipt', [txHash]);
      if (!receipt) {
        throw new Error(`Transaction receipt for ${txHash} not found`);
      }
      
      return {
        transactionHash: receipt.transactionHash,
        transactionIndex: parseInt(receipt.transactionIndex, 16),
        blockHash: receipt.blockHash,
        blockNumber: parseInt(receipt.blockNumber, 16),
        from: receipt.from,
        to: receipt.to,
        cumulativeGasUsed: parseInt(receipt.cumulativeGasUsed, 16),
        gasUsed: parseInt(receipt.gasUsed, 16),
        contractAddress: receipt.contractAddress,
        logs: receipt.logs,
        status: receipt.status
      };
    }
  • TypeScript interface defining the structure of the transaction receipt object returned by the helper method.
    export interface Receipt {
      transactionHash: string;
      transactionIndex: number;
      blockHash: string;
      blockNumber: number;
      from: string;
      to: string | null;
      cumulativeGasUsed: number;
      gasUsed: number;
      contractAddress: string | null;
      logs: any[];
      status: string;
    }
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 for behavioral disclosure. While 'Get' implies a read operation, the description doesn't mention authentication requirements, rate limits, error conditions, or what format the receipt returns. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 maximally concise at just 5 words, front-loading the essential purpose with zero wasted language. Every word earns its place in this efficiently structured description.

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 insufficiently complete. It doesn't explain what a transaction receipt contains, what format it returns, or how it differs from related transaction tools. The minimal description leaves too many contextual questions unanswered.

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 both parameters thoroughly. The description adds no additional parameter context beyond what's in the schema (e.g., hash format, RPC URL defaults). With complete schema coverage, 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 action ('Get') and target resource ('transaction receipt by hash'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_transaction' or 'arbtrace_transaction' that might also retrieve transaction-related data, preventing a perfect score.

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_transaction' and 'arbtrace_transaction' available, there's no indication of what distinguishes this receipt-fetching tool from those other transaction-related tools.

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/dewanshparashar/arbitrum-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server