Skip to main content
Glama

BRAINIAC Base Chain Data

Get block by number or hash

chain-data_block_get

Retrieve a specific block by number or hash from Base Mainnet. Supports optional full transaction details. Price $0.02 USDC. POST /api/v1/chain-data/block/get. 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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockHashNo
blockNumberNo
fullTransactionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does disclose real behavior: per-call price ($0.02 USDC), the POST endpoint, and that unpaid calls return 402 without executing. It omits what happens when the requested block does not exist, and does not say which identifier wins if both blockHash and blockNumber are passed.

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 core action before operational details; no filler. The telegraphic fragments ('Price $0.02 USDC. POST /api/v1/...') are efficient rather than padded, though the endpoint path is of limited value to an agent calling through MCP.

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 three-parameter, no-output-schema, no-annotation tool, the definition covers purpose, cost, and payment failure mode, but leaves the return shape and the identifier-exclusivity rule unexplained. An agent could call it, but could not reliably predict what it gets back or how to handle a missing block.

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%, so the description must compensate, and it partially does: 'by number or hash' maps to blockNumber/blockHash and 'optional full transaction details' maps to fullTransactions. It adds no meaning about mutual exclusivity, precedence between the two identifiers, or the fact that all three are optional and the call would be ambiguous with none supplied.

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 a specific block by number or hash') and pins the network ('Base Mainnet'), which implicitly separates it from chain-data_block_latest. It does not explicitly name the nearest sibling, but the qualifier 'specific' does the differentiating work.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing tells the agent to prefer this over chain-data_block_latest when the block number is unknown, or to use chain-data_block_transactions instead. The only situational content is the payment/402 note, which is about invocation cost, not tool selection.

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