Skip to main content
Glama

AutoTasker Hub — China Social Data API

bitcoin_fees

Bitcoin network fee estimates (fastest/half-hour/hour/economy) via mempool.space. $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does add two real facts beyond the name: the upstream source (mempool.space) and the per-call cost ($0.01 USDC), which is material for a pay-per-call tool. It does not say whether results are cached, how fresh they are, or in what units the fees are reported, so disclosure is partial rather than rich.

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?

Two short sentences, zero filler, with the resource and its tier breakdown front-loaded before the source and cost details. Nothing would be lost by neither adding nor removing text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter read tool this is close to sufficient, but with no output schema the description should say what the return looks like — e.g. per-tier fee rates in sat/vB — and how current they are. The cost and source are covered; the response shape is not.

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 nothing for the description to disambiguate; the baseline for a parameterless schema applies. The tier names in the description effectively document the output categories, which adds a little value.

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?

States a specific resource (Bitcoin network fee estimates) and enumerates the four speed tiers returned (fastest/half-hour/hour/economy), so an agent knows exactly what data comes back. It stops short of differentiating itself from sibling crypto tools like btc_usd_rate or chain_stats, which is the only thing keeping it from a 5.

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 explicit when-to-use or when-not-to-use guidance and no alternative named. Usage is only implied by the enumerated tiers and the data source; an agent must infer that this is for transaction-fee planning rather than price lookup.

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.