Skip to main content
Glama
Sign In
bitmap-mcp

bitmap-mcp

Official
by BitmapAsset
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Bitcoin fee estimates

get_fees

Get current recommended Bitcoin transaction fee estimates in sat/vB, including fastest, half hour, hour, economy, and minimum rates.

Instructions

Return current recommended Bitcoin transaction fee estimates in sat/vB (fastest, half hour, hour, economy, minimum).

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 observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It accurately indicates a read-only operation ('Return') and specifies output categories, but does not mention authentication, rate limits, or potential side effects. For this simple getter, this is adequate and provides full disclosure of the tool's behavior.

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?

One sentence, front-loaded with the action and resource, no wasted words. It is concise and well-structured.

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?

The description fully specifies the return values (sat/vB with five categories), which is sufficient for a zero-param tool with no output schema. It doesn't need to explain parameters or side effects, making it complete for its complexity.

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?

There are zero parameters, and the schema coverage is 100% (vacuously). The description correctly focuses on the output rather than parameters, so it provides no additional parameter semantics needed. This aligns with the baseline for a tool with no parameters.

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 uses a specific verb ('Return') and identifies the exact resource ('Bitcoin transaction fee estimates') with units (sat/vB) and categories (fastest, half hour, hour, economy, minimum). This clearly distinguishes it from sibling tools that handle other Bitcoin data types like blocks, runes, or inscriptions.

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?

The description implies usage—if you need current fee estimates, use this tool—but it does not explicitly state when to use it versus alternatives or mention exclusions. Sibling tools are about different resources, so context is clear, but explicit guidance is absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools