Skip to main content
Glama

21btc.cc Bitcoin Data

Bitcoin network stats

get_network_stats
Read-onlyIdempotent

Bitcoin network now: block height, hashrate (EH/s), difficulty and the next difficulty adjustment, mempool size, average block time, halving countdown. Sources: mempool.space, blockchain.info, Blockchair. Read-only.

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": "get_network_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, and the description's 'Read-only' merely restates that. The added value is the source disclosure (mempool.space, blockchain.info, Blockchair), which tells the agent where the data originates, but it says nothing about caching, refresh cadence, or failure behavior if a source is down.

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?

A single dense sentence front-loads the metric list, followed by a short provenance clause and a one-word safety tag. No filler, and the most decision-relevant content (what you get back) comes first.

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?

There is no output schema, so the description must carry return-value disclosure, which it does by naming each metric. It falls short of complete by omitting units for mempool size and difficulty adjustment timing, plus any note on data freshness or aggregation window.

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, and the description correctly makes no parameter claims. Baseline 4 applies; the explicit unit callout for hashrate (EH/s) shows attention to output semantics rather than input semantics.

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?

Names the exact resource (Bitcoin network) and enumerates the specific metrics returned: block height, hashrate in EH/s, difficulty plus next adjustment, mempool size, average block time, halving countdown. That enumeration cleanly separates it from siblings like get_price, get_fees and get_volatility, which an agent could otherwise confuse with a 'network stats' call.

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

Usage Guidelines2/5

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

The description contains no guidance on when to call this versus alternatives; the word 'now' only hints at a live snapshot. With 13 siblings including get_price, get_fees and get_volatility, an explicit routing statement (e.g. 'use this for chain-level health, not price/fee quotes') would be needed for a higher score.

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