Skip to main content
Glama

21btc.cc Bitcoin Data

Bitcoin transaction fees

get_fees
Read-onlyIdempotent

Recommended Bitcoin transaction fees in sat/vB (fastest, 30 minutes, 1 hour, economy, minimum) and mempool size, from mempool.space. 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_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The 'Read-only' sentence merely restates readOnlyHint=true, so it earns no credit. What does add value is disclosing the upstream source (mempool.space) and the shape of the returned fee tiers, which matters because no output schema exists; caching or freshness behavior is not mentioned.

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 front-loaded sentence listing what is returned, followed by a short safety/source note. No filler, and the most useful information 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?

For a simple, zero-argument read tool with rich annotations, the description covers what is returned and where the data comes from. Only data freshness or rate-limit behavior from mempool.space is left unaddressed, which is minor.

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, so there is no parameter semantics to convey; the baseline for a parameterless tool applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (recommended Bitcoin transaction fees) and enumerates the returned tiers, so an agent knows exactly what it gets. It does not explicitly separate itself from the closest sibling, get_network_stats, which plausibly also covers mempool data.

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?

There is no statement of when to call this versus alternatives; the mempool-size portion overlaps conceptually with get_network_stats and nothing disambiguates them. The only contextual cue is the external source (mempool.space).

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