Skip to main content
Glama

BRAINIAC Base Chain Data

Get block transactions

chain-data_block_transactions

Retrieve all transactions included in a specific block by number or hash from Base Mainnet. Price $0.03 USDC. POST /api/v1/chain-data/block/transactions. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chain-data_block_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockHashNo
blockNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 disclose non-obvious behavior: a $0.03 USDC price, the POST endpoint, and that unpaid calls return 402 and do not execute. It omits what happens for a nonexistent block, whether results are paginated, and whether the call is read-only in effect.

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?

Four short sentences, front-loaded with the purpose, then cost, endpoint, and failure mode. Nothing is padded, though the raw endpoint path adds little for an agent that already has the tool name.

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

Completeness3/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 no output schema and no annotations, the definition covers cost and failure but leaves the return shape (which transaction fields come back) and result-size/pagination behavior entirely unstated.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and only partially does: 'by number or hash' maps loosely to blockNumber and blockHash. It never says the parameters are optional, whether they are mutually exclusive, which wins if both are supplied, or the expected hash format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Retrieve all transactions included in a specific block') plus the network (Base Mainnet) and the two lookup keys. It is distinguishable from chain-data_block_get by returning transactions rather than block metadata, though it never names a sibling explicitly.

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: an agent can infer it should call this when it needs the transaction list of a known block. There is no statement of when to prefer it over chain-data_block_get or chain-data_transaction_receipt, and no guidance on which of the two lookup keys to choose.

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