Skip to main content
Glama

BRAINIAC Base Chain Data

Get latest block

chain-data_block_latest

Retrieve the latest block information from Base Mainnet using the public JSON-RPC endpoint. Price $0.02 USDC. POST /api/v1/chain-data/block/latest. 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_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 delivers meaningful operational detail: the network (Base Mainnet), transport (public JSON-RPC, POST), cost ($0.02 USDC), and the failure mode that unpaid calls return 402 without executing. It omits anything about rate limits, caching/staleness of the result, or the shape of the returned block.

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 before pricing and transport details. The literal endpoint path is arguably redundant with the tool name, but it is compact and costs little.

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?

For a zero-parameter read with no output schema and no annotations, the description covers everything needed to decide and invoke: what it returns, which network, how it is billed, and what happens when unpaid. Only the block's return fields and result freshness are left unstated, which is a minor gap for a well-understood primitive.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies.

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?

"Retrieve the latest block information" gives a specific verb and resource, and "latest" implicitly separates it from chain-data_block_get, which presumably targets a block by number or hash. It stops short of naming that sibling explicitly, so the differentiation is inferred rather than stated.

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?

The word "latest" implies the usage context (current chain head), but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for fetching a specific block. An agent must infer the routing from sibling names alone.

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