Skip to main content
Glama

Check an EVM transaction's status, fee and token transfers

evm_tx
Read-only

Status, block, time, sender, recipient, value, gas used and fee (native and USD) of an EVM transaction, plus the ERC-20 Transfer events inside it (token, symbol, from, to, amount). A pending transaction returns status pending. Read over public RPC; a fallback node is used when the first refuses old receipts. Related tools on this server, for a different need: evm_balance when you need ERC-20 balance of an address for one token contract; evm_nft when you need ERC-721 facts for one token: owner, collection name. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hash": "<hash>"
    },
    "name": "evm_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash, 0x + 64 hex characters
chainNobase (default), ethereum, arbitrum, optimism or polygon

Output Schema

NameRequiredDescriptionDefault
toNo
feeNo
fromNo
hashNo
timeNo
blockNo
chainNo
valueNo
sourceNo
statusNo
gasUsedNo
checkedAtNo
transfersNo
disclaimerNo
nativeSymbolNo
contractCreatedNo
effectiveGasPriceGweiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds several things they cannot: pending transactions return status pending, reads go over public RPC with a fallback node for old receipts the first refuses, and pricing is $0.002 per successful call via x402 with failed calls uncharged. Auth/payment model and failure-cost behavior are exactly the kind of context an agent needs before committing to a paid call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The return-field inventory is front-loaded in the first sentence, followed by the pending-state caveat, the RPC fallback note, sibling routing, and cost. Every clause carries information, though the pricing sentence is long and the return-field enumeration partly duplicates the output schema, making it slightly heavier than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter paid read tool with an output schema and rich annotations, the description covers cost model, pending semantics, node fallback, and sibling routing — nothing an agent needs is missing. It is slightly over-complete on return fields that the output schema already supplies, but that is redundancy rather than a gap.

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 coverage is 100%, with both hash format and the chain value list already documented in the schema. The description adds nothing about parameters — it neither restates the chain default nor explains hash formatting — so the baseline of 3 applies; the schema does the work here.

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

Purpose5/5

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

The description names the exact resource (an EVM transaction) and enumerates what is returned: status, block, time, sender, recipient, value, gas used, fee in native and USD, plus ERC-20 Transfer events. It also distinguishes itself from evm_balance and evm_nft by naming the different need each serves, so an agent can pick correctly without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Guidance is implicitly clear from the enumerated outputs, and the 'Related tools on this server, for a different need' sentence explicitly routes the agent to evm_balance for token balances and evm_nft for ERC-721 facts. There is no explicit 'use this when' clause or exclusion for the closest-looking siblings evm_transfers and evm_logs, which is the remaining gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources