Skip to main content
Glama

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

Base transaction receipt

base_receipt
Read-only

Transaction receipt on Base (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 base_tx. Input is a 0x-prefixed 64-hex hash; a pending or unknown hash returns 422, uncharged. Example: hash=0x7d108fa131ed949c76d50caf2e7dfe25fc9903b9d276c40a0446d8afbdfe86b0. 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": "base_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYes0x-prefixed transaction hash (64 hex characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/destructive/idempotent, but the description adds material behavior: 422 on pending or unknown hashes, that such calls are uncharged, per-call pricing, 25 free calls, and failed calls free. It also explains that repeats are charged, which is exactly the context behind idempotentHint=false.

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, then cost. Slightly dense on pricing/payment boilerplate and the clause "Reads or computes only and changes nothing" restates readOnlyHint, but no sentence is truly wasted.

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?

No output schema exists, yet the description enumerates the returned fields, the error condition, and the cost model, so an agent knows both what it gets and what it pays. Nothing needed to call it correctly is missing for a single-parameter receipt lookup.

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 a concrete example hash and the semantic rule that a 0x-prefixed 64-hex hash that is pending or unknown yields 422. That exceeds what the schema's format note conveys, though it stops short of further hash validation details.

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 ("Transaction receipt on Base", eth_getTransactionReceipt) and enumerates the returned fields: status, gas used, effective gas price, fee in ETH, log count, contract created. It explicitly contrasts itself with base_tx ("for sender, value and calldata use base_tx"), so an agent can separate it from the nearest sibling without opening either 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 an explicit use case ("confirm a payment or call went through") and names the alternative for the other need (base_tx for sender/value/calldata). It also states the negative case: a pending or unknown hash returns 422 and is uncharged, which tells the agent what not to expect.

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.