Skip to main content
Glama

Recommended Bitcoin fees in sat/vB, the mempool's size

btc_fees
Read-only

Recommended Bitcoin fees in sat/vB (fastest, 30 minutes, 1 hour, economy, minimum), the mempool's size and count, and what a typical 140 vB transaction costs in BTC and USD. Source: mempool.space; USD from Coinbase spot. Cached 30 seconds. Information only, not financial advice. Related tools on this server, for a different need: btc_tx when you need to check a Bitcoin transaction's status, fee and size; btc_address when you need a Bitcoin mainnet address: confirmed and unconfirmed. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
btcUsdNo
sourceNo
mempoolNo
checkedAtNo
disclaimerNo
feesSatPerVbyteNo
typicalTransactionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context the agent needs: upstream sources (mempool.space, Coinbase spot for USD), a 30-second cache window, and explicit billing terms ($0.002 per successful call via x402, failed calls not charged). The cached-30s detail matters because it tells the agent results may be slightly stale.

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?

Front-loaded with the core capability and fee tiers, then sources, caching, disclaimer, sibling routing, and payment mechanics in a logical order. The pricing/payment sentence is long but is operationally relevant; the 'not financial advice' clause is boilerplate but brief.

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?

An output schema exists, so return-value detail is not required, yet the description still previews the tier names and the 140 vB cost calculation. Sources, cache TTL, cost model, and alternatives are all covered, leaving no material gap for a zero-parameter read tool.

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 no parameters, so parameter semantics carry a 4 baseline. The description does enumerate the fee tiers and the representative transaction size, which prepares the agent for what the output covers even though the output schema formally documents returns.

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 a specific resource and verb: recommended Bitcoin fees in sat/vB broken out by five tiers, plus mempool size/count and the cost of a typical 140 vB transaction in BTC and USD. This is unmistakably a fee-estimation tool, distinct from the transaction-status and address siblings.

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?

Explicitly routes the agent elsewhere: btc_tx for transaction status/fee/size verification and btc_address for mainnet address data, framed as 'for a different need.' It stops short of stating exclusions for this tool itself (e.g., don't use it when you need historical fee data), but the context is clear.

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