Skip to main content
Glama

BRAINIAC Base Chain Data

Get transaction receipt

chain-data_transaction_receipt

Retrieve the receipt and status for a specific transaction on Base Mainnet, including logs and gas used. Price $0.02 USDC. POST /api/v1/chain-data/transaction/receipt. Unpaid calls return 402 and do not run.

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": {
      "txHash": "<txHash>"
    },
    "name": "chain-data_transaction_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
txHashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the paid endpoint ($0.02 USDC), the HTTP method, and the failure mode (unpaid calls return 402 and do not execute). It stops short of stating what happens for pending, unknown, or unconfirmed transactions, which is the main behavioral gap.

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 short sentences with the purpose and return contents front-loaded; price and payment failure follow logically. The raw endpoint path is marginal information but does carry the POST method, so it broadly earns its place.

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, and the description compensates by naming the returned fields (receipt, status, logs, gas used), plus the payment precondition. For a single-parameter read tool this is close to complete; only edge-case behavior and response framing are absent.

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 0%, but the single parameter has a strict regex pattern (^0x[0-9a-fA-F]{64}$) that already conveys the expected 32-byte hex hash format. The description adds no further meaning about txHash (e.g. chain scoping, case handling) beyond what the schema establishes.

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 ('Retrieve the receipt and status for a specific transaction') plus the network scope (Base Mainnet) and payload contents (logs and gas used). That is enough for an agent to distinguish it from siblings such as chain-data_block_get or chain-data_logs_search without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer it should call this when it has a tx hash and wants receipt data rather than block or log data. There is no explicit when-to-use/when-not guidance and no alternative named (e.g. logs_search for log-only queries).

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