Skip to main content
Glama

get_transaction

Retrieve detailed blockchain transaction information by providing a transaction hash to access data like sender, receiver, amount, and status.

Instructions

Get transaction details by hash

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashYesThe transaction hash

Implementation Reference

  • index.ts:874-887 (registration)
    Registration of the 'get_transaction' tool, including its name, description, and input schema definition.
    {
      name: "get_transaction",
      description: "Get transaction details by hash",
      inputSchema: {
        type: "object",
        properties: {
          hash: {
            type: "string",
            description: "The transaction hash",
          },
        },
        required: ["hash"],
      },
    },
  • TypeScript type definition for the input parameters of the get_transaction tool.
    type GetTransactionParams = { hash: string };
  • Validator function to check if arguments match GetTransactionParams for the get_transaction tool.
    const isValidGetTransactionParams = (
      args: any
    ): args is GetTransactionParams => {
      return (
        typeof args === "object" && args !== null && typeof args.hash === "string"
      );
    };
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it retrieves details but doesn't describe what 'details' include (e.g., sender, receiver, amount, status), whether it's a read-only operation, error handling for invalid hashes, or performance characteristics like rate limits. This leaves significant gaps 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 extremely concise with a single, clear sentence that front-loads the essential information. There is no wasted verbiage, making it easy to parse quickly while conveying the core functionality.

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 for effective tool use. It doesn't explain what transaction details are returned (e.g., fields, data structure), error conditions, or how it differs from sibling tools. For a data retrieval tool with no structured output documentation, this leaves too many unknowns.

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 minimal value beyond the input schema, which has 100% coverage and fully documents the single 'hash' parameter. The description mentions 'by hash' but doesn't provide additional context like hash format, length, or examples. With high schema coverage, the baseline score of 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 tool's purpose with a specific verb ('Get') and resource ('transaction details'), specifying it retrieves details by hash. It distinguishes from some siblings like 'get_transaction_receipts' by focusing on transaction details rather than receipts, but doesn't explicitly differentiate from all similar tools like 'get_block_with_transactions'.

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 doesn't mention when to choose this over 'get_transaction_receipts' for receipt information or 'get_block_with_transactions' for block context, nor does it specify prerequisites like needing a valid transaction hash.

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