Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

get_transaction_receipt

Read-onlyIdempotent

chainpeek: Get a transaction receipt on Ethereum, Base or Robinhood Chain. For value, nonce and confirmations too use get_transaction; for decoded events use decode_tx_logs. Returns the receipt of a mined transaction. An unknown or pending hash is a 200 with status: not_found. One to four RPC reads (the finality tags fresh). Ethereum, Base and Robinhood only. Read-only. Reads are cached up to 30 s. A bad hash is a 422 before any payment (not charged). An unknown or pending hash is charged like any answer. Typically under 1 s. Price: USD 0.002. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/ethereum-rpc-reads-api.html

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": {
      "chain": "<chain>",
      "hash": "<hash>"
    },
    "name": "get_transaction_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash (0x + 64 hex).
chainYesethereum, base or robinhood (Robinhood Chain, chain id 4663).

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
hashNo
typeNo
blockNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
statusNo
fee_weiNo
finalityNo
gas_usedNo
log_countNo
timestampNo
block_hashNo
l1_fee_weiNo
block_age_sNo
status_noteNo
contract_addressNo
transaction_indexNo
cumulative_gas_usedNo
effective_gas_price_weiNo
effective_gas_price_gweiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / properties / hash / title
      Removed value: -"Hash"
    • removedInput schema / title
      Removed value: -"get_transaction_receiptArguments"
  2. Changed3 schema fields changed
    • addedOutput schema / properties / block_age_s
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / finality
      Added value: +{
      +  "enum": [
      +    "finalized",
      +    "safe",
      +    "unsafe",
      +    null
      +  ],
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / timestamp
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"ethereum or base."New value: +"ethereum, base or robinhood (Robinhood Chain, chain id 4663)."
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "ethereum",
      -  "base"
      -]New value: +[
      +  "ethereum",
      +  "base",
      +  "robinhood"
      +]
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover read-only/idempotent safety, but the description adds substantial behavior beyond them: one to four RPC reads with finality tagging, 30 s cache window, 422 on malformed hash before payment, charging behavior for unknown/pending hashes, sub-second latency, and price plus free-tier limits. These are exactly the cost and failure-mode facts an agent needs before spending money.

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?

Purpose and sibling routing are front-loaded, and every clause carries a distinct operational fact. It is dense and slightly run-on, with pricing, free-tier, latency, and a docs URL stacked at the end, but no sentence is pure filler.

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

Completeness5/5

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

For a two-parameter read tool with a full schema, an output schema, and rich annotations, the description covers the remaining gaps: chain coverage, failure semantics for bad and unknown hashes, cost, and caching. Nothing an agent needs to invoke or budget for the call is missing.

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 hash pattern and chain enum fully documented in the schema itself. The description only restates the supported chains ("Ethereum, Base and Robinhood only"), adding no format or semantic detail beyond the structured fields. 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 and resource ("Get a transaction receipt") plus the exact supported chains, and explicitly distinguishes itself from two named siblings, get_transaction and decode_tx_logs. An agent can select it without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules: use get_transaction for value/nonce/confirmations, use decode_tx_logs for decoded events. It also states the negative case (unknown or pending hash returns a 200 with status: not_found) so the agent knows what a non-result looks like.

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.