Skip to main content
Glama

APEX DeFi, DefiLlama & 8-Chain EVM Intel

Evm tx

evm_tx
Read-onlyIdempotent

Transaction status and receipt by hash across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood): success or revert, from, to, value, contract created, gas used, fee paid, block and time. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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)
chainNoethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the bar is lower, yet the description still adds material context the annotations do not carry: the $0.002 per-call price, the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the two-step x402 handshake. The only gap is error behavior for an unknown or pending hash.

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?

Three front-loaded sentences with no filler: what you get, what it costs, and how to pay. The chain and return-field enumerations are dense but justified. The third sentence restates the payment mechanics already implied by the second, a minor redundancy.

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?

There is no output schema, so the description carries full responsibility for return values, and it delivers with an explicit receipt field list. Payment setup, pricing and chain coverage are all present. Remaining gaps are edge-case behavior such as pending transactions, unindexed hashes or revert error reporting.

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%, so the schema already documents hash format, the eight chain values including ethereum as default, and the PAYMENT-SIGNATURE payload. The description reinforces how `payment` is used within the call flow but does not add format or syntax detail beyond what the structured fields already give. Baseline 3 applies.

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?

States a specific verb+resource (transaction status and receipt by hash) and enumerates exactly what the receipt contains: success/revert, from, to, value, contract created, gas used, fee paid, block and time. The 'by hash' scope, plus the single-transaction framing, is enough to distinguish it from the batch sibling tx_batch_status without naming it.

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?

The payment workflow is spelled out in operational terms: call once without `payment` to get terms, sign with your own wallet, call again with `payment`. That is clear procedural context. It stops short of tool-selection guidance, e.g. pointing to tx_batch_status when multiple hashes need checking.

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.