Skip to main content
Glama
dcSpark

MCP Crypto Wallet EVM

by dcSpark
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

provider_get_transaction_receipt

Retrieve a transaction receipt from Ethereum or EVM-compatible blockchains using the transaction hash to confirm details like status, logs, and gas used.

Instructions

Get a transaction receipt

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transactionHashYesThe transaction hash

Implementation Reference

  • src/handlers/wallet.ts:538-555 (handler)
    The handler function that executes the tool logic by retrieving the transaction receipt using the provider.
    export const getTransactionReceiptHandler = async (input: any): Promise<ToolResultSchema> => {
  try {
    if (!input.transactionHash) {
      return createErrorResponse("Transaction hash is required");
    }

    const provider = getProvider();
    const receipt = await provider.getTransactionReceipt(input.transactionHash);

    return createSuccessResponse(
    `Transaction receipt retrieved successfully
      Transaction hash: ${input.transactionHash}
      Transaction receipt: ${receipt}
    `);
  } catch (error) {
    return createErrorResponse(`Failed to get transaction receipt: ${(error as Error).message}`);
  }
};
  • src/tools.ts:414-424 (schema)
    The input schema definition for the provider_get_transaction_receipt tool.
    {
  name: "provider_get_transaction_receipt",
  description: "Get a transaction receipt",
  inputSchema: {
    type: "object",
    properties: {
      transactionHash: { type: "string", description: "The transaction hash" }
    },
    required: ["transactionHash"]
  }
},
  • src/tools.ts:592-592 (registration)
    The registration of the handler in the tools handlers dictionary.
    "provider_get_transaction_receipt": getTransactionReceiptHandler,

Tool Definition Quality

C2.7/5.0
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 but only states the basic action. It doesn't mention whether this is a read-only operation, if it requires network access, potential error conditions (e.g., invalid hash), or what the receipt contains (e.g., status, gas used). This leaves significant gaps for a tool that interacts with blockchain data.

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—a single, direct sentence with no wasted words. It's front-loaded with the core action, making it easy to parse quickly, though this brevity contributes to gaps in other dimensions.

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 of blockchain transactions and the lack of annotations or output schema, the description is incomplete. It doesn't explain what a transaction receipt entails (e.g., success/failure status, logs) or behavioral aspects like idempotency or error handling, which are crucial for effective tool use in this domain.

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 the parameter 'transactionHash' clearly documented in the schema. The description doesn't add any additional meaning beyond what the schema provides (e.g., format examples or constraints), so it meets the baseline for adequate but unenhanced parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get a transaction receipt' clearly states the verb ('Get') and resource ('transaction receipt'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'provider_get_transaction' or 'provider_get_logs', leaving ambiguity about what specifically distinguishes this tool from related operations.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites (e.g., needing a transaction hash from a sent transaction) or comparisons to siblings like 'provider_get_transaction', leaving the agent to infer usage without explicit direction.

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

Related 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/dcSpark/mcp-cryptowallet-evm'

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