Skip to main content
Glama
teamssUTXO

Bitcoin-MCP-Server

get_bitcoin_network_overview

Get current Bitcoin network status including price, hashrate, difficulty, blocks, transactions, mining economics, and supply data to monitor blockchain health and activity.

Instructions

Use this for general Bitcoin blockchain questions about current state, health, or status.

Provides comprehensive network overview across five key areas:

**Network Statistics:**
- Current market price in USD
- Network hashrate in TH/s (total mining power)
- Current mining difficulty
- Next difficulty adjustment block height

**Block Metrics:**
- Blocks mined in the last 24 hours
- Total blocks in the blockchain
- Average time between blocks (target: 10 minutes)
- Average block size in bytes

**Transaction Activity:**
- Total transactions in the last 24 hours
- Estimated BTC sent in 24h
- Estimated transaction volume in USD

**Mining Economics:**
- BTC mined in the last 24 hours (new supply)
- Total transaction fees collected in 24h (in BTC)
- Total miner revenue in BTC and USD

**Supply Information:**
- Total BTC in circulation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses behavioral traits by listing the specific data areas returned (e.g., network statistics, block metrics), which helps the agent understand what information to expect. However, it lacks details on rate limits, error conditions, or data freshness, leaving some behavioral aspects unclear for a tool with no annotation coverage.

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 front-loaded with a clear purpose statement, followed by a bullet-point breakdown of the five key areas, each with specific metrics. Every sentence and bullet point earns its place by providing essential information without redundancy, making it highly efficient and well-structured.

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 tool's complexity (providing a multi-faceted overview), no annotations, and an output schema exists, the description is complete enough. It thoroughly explains what data is returned across five areas, compensating for the lack of annotations and leveraging the output schema for return value details. This ensures the agent can understand the tool's scope and use it effectively.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on output semantics by detailing the five key areas of data returned, adding value beyond the schema. A baseline of 4 is applied since no parameters exist, and the description compensates by explaining the output structure.

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's purpose: to provide a comprehensive network overview for general Bitcoin blockchain questions about current state, health, or status. It specifies the verb ('provides') and resource ('comprehensive network overview') while distinguishing itself from siblings by focusing on multi-area status rather than specific data points like price, blocks, or addresses.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('for general Bitcoin blockchain questions about current state, health, or status') and implies when not to use it by listing five key areas it covers, suggesting alternatives like get_bitcoin_price_usd or get_10_latest_blocks_informations for more specific queries. This provides clear context and exclusions.

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-Server'

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