Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Ethereum transaction receipt

eth_receipt
Read-only

Transaction receipt on Ethereum (eth_getTransactionReceipt): success or reverted, gas used, effective gas price, fee paid in ETH, number of event logs and any contract created. Use to confirm a payment or call went through; for sender, value and calldata use eth_tx. Input is a 0x-prefixed 64-hex hash; a pending or unknown hash returns 422, uncharged. Example: hash=0x9531467e03a57bbb5cd080439ac3b10c0cefed147282eb2ff709b02c897afcbf. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "eth_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYes0x-prefixed transaction hash (64 hex characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the failure mode for pending/unknown hashes (422, uncharged), the pricing model (per-call charge, first 25 free, failed calls free), and the fact that repeated calls are re-billed — which usefully explains the idempotentHint=false annotation. It stops short of describing the response payload shape, but the read-only/no-side-effects guarantee is stated clearly.

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?

Front-loaded with purpose and return fields, then usage routing, then input/error behavior, then cost. The billing note is slightly duplicated ('first 25 free; failed calls free' followed by 'each call is charged, so repeats are not free'), but each sentence otherwise carries weight.

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?

There is no output schema, yet the description enumerates the meaningful return fields, so an agent knows what it will get. Combined with input format, error behavior, and pricing, nothing essential is missing for a single-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real value: it restates the 0x-prefixed 64-hex format, supplies a concrete example hash, and defines what happens when the hash resolves to a pending or unknown transaction. That error semantics is not in the schema.

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?

Names the specific RPC method (eth_getTransactionReceipt) and enumerates exactly what comes back: status (success/reverted), gas used, effective gas price, fee in ETH, log count, and any created contract. It also explicitly differentiates from the sibling eth_tx, so an agent can pick between them without opening a 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 a concrete use case ('confirm a payment or call went through') and names the alternative with the condition that selects it ('for sender, value and calldata use eth_tx'). That is explicit when-to-use plus a routing rule to a sibling.

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.