Skip to main content
Glama
teamssUTXO

Bitcoin-MCP-Server

get_bitcoin_network_overview

Fetch current Bitcoin network status: price, hashrate, difficulty, block metrics, transaction volume, mining revenue, and circulating supply. Essential for assessing network health.

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
Behavior4/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 thoroughly describes all returned data across five categories, making the tool's behavior transparent. It does not mention side effects, rate limits, or data freshness, but as a read-only query, the output description is largely sufficient.

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?

The description is well-structured with clear headings and bullet points, front-loading the purpose. It is comprehensive but could be slightly more concise; however, the level of detail is appropriate for the tool's scope.

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?

Given that the tool has no parameters and an output schema (not shown but present), the description is complete in explaining the returned data across all five areas. It could add notes on data recency or limitations, but overall it provides sufficient context for agent selection.

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 zero parameters, so the description does not need to add parameter semantics. The baseline for zero-parameter tools is 4, and the description correctly avoids any misleading parameter references.

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: for general Bitcoin blockchain questions about current state, health, or status. It lists five specific areas with detailed data points, distinguishing it from sibling tools that cover narrower topics like market data or network health.

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 opens with 'Use this for general Bitcoin blockchain questions,' providing clear usage context. However, it does not explicitly mention when not to use this tool or list alternative sibling tools for more specific 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