Skip to main content
Glama
teamssUTXO

Bitcoin-MCP-Server

get_10_latest_blocks_informations

Retrieve detailed data on the last 10 Bitcoin blocks, including transaction count, fees, reward, and mining pool. Use to analyze blockchain activity trends.

Instructions

Use this to get detailed information and statistics about the 10 most recently mined Bitcoin blocks.

Returns comprehensive metrics in string format for each of the last 10 blocks:
- Block height and unique identifier (hash)
- Mining timestamp
- Transaction count
- Block size (in MB) and weight
- Total fees collected and average fee rate (sat/vB)
- Block reward (in satoshis)
- Mining pool that found the block
- Nonce value

Also includes aggregate statistics across all 10 blocks:
- Total number of transactions
- Average transactions per block
- Average block size
- Average time between blocks (in minutes)

Use cases: When you need to analyze recent blockchain activity trends, compare mining pool performance, or monitor network congestion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so the description carries the full burden. It thoroughly discloses the return format and enumerates all data fields and aggregate statistics. It does not mention rate limits or authentication, but for a read-only tool this is sufficient.

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 efficiently structured with a clear purpose statement followed by a bulleted list of returned metrics. Every sentence adds value, and it is appropriately sized for the tool's complexity.

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 zero parameters and an existing output schema, the description fully explains what the tool returns and why it is useful. It covers both individual block data and aggregate statistics, making it complete for an agent to understand its functionality.

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 has no parameters, so the description adds value by explaining the output structure. Schema coverage is 100%, baseline for 0 parameters is 4, and the description meets this well.

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 detailed information about the 10 most recently mined Bitcoin blocks, listing specific metrics and aggregate statistics. It distinguishes from sibling tools like get_summary_of_latest_block by specifying the scope (10 blocks).

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?

The description provides explicit use cases (analyze trends, compare pool performance, monitor congestion) and implies when to use the tool. However, it does not mention when not to use it or point to alternative tools for single-block queries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/teamssUTXO/bitcoin_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server