Skip to main content
Glama

CoinVet

Bitcoin fee estimates (sat/vB)

mempool_fees
Read-onlyIdempotent

Recommended Bitcoin on-chain fee rates in sat/vB (next block, ~30 min, ~1 h, economy, minimum), mempool size, current block height, and the example cost in sats of a typical 140 vB transaction.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds value by disclosing the exact shape of the payload (five fee tiers plus mempool size, block height, and a 140 vB cost example), which tells the agent what to expect without calling it. It does not discuss caching or staleness of fee data.

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?

A single dense sentence front-loads the core resource and then enumerates outputs. Every clause earns its place, but the sentence is long and could be split into purpose plus return-value structure for easier scanning.

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?

With no input parameters and no output schema, the description carries the full burden of describing return values, and it does so by naming all five fee tiers and the auxiliary fields. It is essentially complete, with only minor gaps around data freshness and units for mempool size.

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 the baseline is 4. There is nothing for the description to disambiguate, and the schema is trivially complete.

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 a specific resource (Bitcoin on-chain fee rates in sat/vB) and enumerates the returned data: tiered fee estimates, mempool size, block height, and example tx cost. It is unambiguous about what the tool provides, though it does not explicitly distinguish itself from siblings such as btc_price, since no similar fee tool exists.

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

Usage Guidelines3/5

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

Usage is implied by the content — an agent can infer this is the tool for fee estimation — but there is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. No prerequisites or caveats about freshness of the estimate are stated.

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