Skip to main content
Glama

get_transaction_receipts

Retrieve transaction receipts for a specific blockchain block using either block hash or block number to verify transaction outcomes and status.

Instructions

Get transaction receipts for a block

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blockHashNoThe hash of the block
blockNumberNoThe number of the block

Implementation Reference

  • index.ts:830-847 (registration)
    Registration of the get_transaction_receipts tool in the ListToolsRequestSchema handler, including name, description, and detailed inputSchema for blockHash or blockNumber.
    {
      name: "get_transaction_receipts",
      description: "Get transaction receipts for a block",
      inputSchema: {
        type: "object",
        properties: {
          blockHash: {
            type: "string",
            description: "The hash of the block",
          },
          blockNumber: {
            type: "string",
            description: "The number of the block",
          },
        },
        oneOf: [{ required: ["blockHash"] }, { required: ["blockNumber"] }],
      },
    },
  • Type definition for the input parameters of get_transaction_receipts, aliasing Alchemy SDK's TransactionReceiptsParams.
    type GetTransactionReceiptsParams = TransactionReceiptsParams;
  • Helper validation function to type-guard and validate the input arguments for the get_transaction_receipts tool.
    const isValidGetTransactionReceiptsParams = (
      args: any
    ): args is GetTransactionReceiptsParams => {
      return (
        typeof args === "object" &&
        args !== null &&
        (args.blockHash !== undefined || args.blockNumber !== undefined) &&
        (args.blockHash === undefined || typeof args.blockHash === "string") &&
        (args.blockNumber === undefined ||
          typeof args.blockNumber === "string" ||
          typeof args.blockNumber === "number")
      );
    };
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 a read operation ('Get') but does not cover aspects like rate limits, authentication needs, error handling, or the format of returned receipts. This is a significant gap for a tool with no annotation coverage.

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, efficient sentence with zero waste. It is front-loaded and appropriately sized for the tool's purpose, making it highly concise and well-structured.

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 no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, return values, and usage context. For a tool with 2 parameters and no structured output, more information is needed to fully guide an AI agent.

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%, with clear descriptions for 'blockHash' and 'blockNumber'. The description adds no additional parameter semantics beyond what the schema provides, such as format details or usage examples. 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.

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 ('transaction receipts for a block'), making the purpose specific and understandable. However, it does not explicitly differentiate from siblings like 'get_transaction' or 'get_block_with_transactions', which might also retrieve transaction-related data, so it misses full sibling distinction.

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. It does not mention prerequisites, exclusions, or compare to siblings such as 'get_transaction' or 'get_block_with_transactions', leaving usage context implied at best.

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/itsanishjain/alchemy-sdk-mcp'

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