Skip to main content
Glama
teamssUTXO

Bitcoin-MCP-Server

get_bitcoin_network_recommended_fees

Get current recommended Bitcoin transaction fees for fastest, half-hour, standard, or economy confirmation. Optimize cost vs. speed based on network congestion.

Instructions

Use this to get current recommended Bitcoin transaction fees for different confirmation speed priorities.

Returns fee recommendations in string format with four priority levels:
- **Fastest** (~10 minutes): Highest fee for next block inclusion
- **Half-hour** (~30 minutes): Medium-high fee for confirmation within 30 min
- **Standard** (~60 minutes): Medium fee for confirmation within 1 hour
- **Economy**: Lowest fee for non-urgent transactions

Each recommendation includes:
- Fee rate in sat/vB (satoshis per virtual byte)
- Estimated confirmation time
- Approximate total cost in BTC for a typical transaction

Fees are dynamic and change based on current network congestion and mempool size.

Use cases: When you need to know how much to pay for a Bitcoin transaction, to optimize transaction costs vs. speed, or to check if the network is congested.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses that fees are dynamic based on network conditions and lists the four priority levels with details. However, it lacks information on rate limits, authentication, or error handling, but these are not critical for a simple read-only tool.

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?

The description is well-structured with bullet points and front-loaded purpose. It is not overly verbose; each sentence adds information. Could be slightly more concise, but still effective.

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?

Given no parameters and an output schema (not shown), the description fully explains the return format, priority levels, and dynamic nature. It covers all necessary context for an agent to use the tool correctly.

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?

No parameters exist (schema coverage 100%). With 0 parameters, the baseline is 4. The description adds value by explaining the output, which is more important than parameter info.

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 clearly states the tool's purpose: 'get current recommended Bitcoin transaction fees for different confirmation speed priorities.' It specifies the resource (Bitcoin transaction fees) and the action (get). Among sibling tools, none overlap, providing clear differentiation.

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?

The description includes explicit use cases: 'When you need to know how much to pay for a Bitcoin transaction, to optimize transaction costs vs. speed, or to check if the network is congested.' It does not mention when not to use, but the narrow scope makes it obvious.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/teamssUTXO/bitcoin_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server