Skip to main content
Glama

mcp-server

by com.blockscout

Get Block Information

get_block_info
Read-only

Get block information like timestamp, gas used, burnt fees, transaction count etc. Can optionally include the list of transaction hashes contained in the block. Transaction hashes are omitted by default; request them only when you truly need them, because on high-traffic chains the list may exhaust the context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chain_idYesThe ID of the blockchain
session_idNoOpaque session identifier.
number_or_hashYesBlock number or hash
include_transactionsNoIf true, includes a list of transaction hashes from the block.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe main data payload of the tool's response.
notesNoA list of important contextual notes, such as warnings about data truncation or data quality issues.
paginationNoPagination information, present only if the 'data' is a single page of a larger result set.
content_textNoOptional human-readable summary used for MCP content responses.
instructionsNoA list of suggested follow-up actions or instructions for the LLM to plan its next steps.
data_descriptionNoA list of notes explaining the structure, fields, or conventions of the 'data' payload.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, so safety is covered. The description adds value by disclosing that transaction hashes are omitted by default and warning about the potential context impact on high-traffic chains, which are behavioral details not present in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the primary purpose, and includes the critical caution about transaction hashes. Every sentence earns its place with no wasted words.

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?

Given the presence of an output schema and strong annotations, the description covers the core functionality, lists representative return fields, and highlights the one notable behavioral caveat. No important aspect is left unexplained.

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 schema already describes all parameters fully, so the baseline is 3. The description adds meaningful context for include_transactions, explaining the cost/benefit beyond the schema's simple boolean description, which improves the semantic understanding.

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?

The description clearly states the tool retrieves block information and lists specific data fields (timestamp, gas used, burnt fees, transaction count). This distinguishes it from siblings like get_block_number, which targets a single piece of data.

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

Usage Guidelines4/5

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

It gives explicit guidance on when to set include_transactions to true, noting the default is omitted and advising to request only when truly needed to avoid context exhaustion. It does not mention alternative tools, but the guidance is clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct blockchain resource or action (address, block, transaction, token, NFT, contract, chain, raw API, session init). Even though direct_api_call is a generic fallback, the specialized tools have clear, non-overlapping purposes, and the complementary nature of tools like get_token_transfers_by_address and get_transactions_by_address is explicitly documented.

Naming Consistency4/5

The majority of tools follow a consistent get_<resource> pattern (e.g., get_block_info, get_tokens_by_address), but there are notable deviations: direct_api_call, lookup_token_by_symbol, inspect_contract_code, read_contract, and __unlock_blockchain_analysis__. These verbs are still descriptive and readable, but the mix of 'get' with other verbs prevents a perfect 5.

Tool Count4/5

With 16 tools, the server is slightly above the ideal 3-15 range but not excessive. Each tool maps to a significant Blockscout API capability, and the count feels proportional to the breadth of blockchain data covered. It is heavier than a minimal toolkit but not bloated.

Completeness4/5

The tool set covers core exploration workflows: address info, block lookup, transaction details, token/NFT holdings, contract ABI/source inspection, and read-only contract calls. Minor gaps like a dedicated token-info-by-contract-address tool exist, but the direct_api_call fallback and get_address_info's token details mitigate these. The surface is comprehensive for a read-only blockchain explorer.

Resources