Skip to main content
Glama
Sign In

Mempool Space

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Recommended Fees

recommended_fees
Read-onlyIdempotent

Current sat/vB fee recommendations.

Input Schema

NameRequiredDescriptionDefault
networkNoWhich Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what "Bitcoin" means in an ordinary question. "bitcoin" and "btc" are accepted as aliases for mainnet.mainnet

Output Schema

NameRequiredDescriptionDefault
hourFeeNoOne-hour fee in sat/vB
economyFeeNoEconomy fee in sat/vB
fastestFeeNoFastest fee in sat/vB
minimumFeeNoMinimum fee in sat/vB
halfHourFeeNoHalf-hour fee in sat/vB

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / network / default
      Added value: +"mainnet"
    • addedInput schema / properties / network / description
      Added value: +"Which Bitcoin network. Defaults to mainnet — the real Bitcoin network, which is what \"Bitcoin\" means in an ordinary question. \"bitcoin\" and \"btc\" are accepted as aliases for mainnet."
    • addedInput schema / properties / network / enum
      Added value: +[
+  "mainnet",
+  "testnet",
+  "signet",
+  "liquid"
+]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive nature. The description adds no further behavioral context (e.g., caching, rate limits, or data freshness). Given thorough annotations, the description's contribution is minimal, earning a baseline score of 3.

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?

The description is a single, concise sentence that front-loads the key information. No unnecessary words or filler, making it efficient for an AI agent to parse.

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?

While the tool has an output schema (handling return values) and a simple input, the description lacks additional context such as network availability, typical fee ranges, or usage patterns. It is minimally adequate but could be more informative about when these recommendations are updated or their reliability.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with a detailed description for the 'network' parameter (including aliases and default). The tool-level description adds nothing beyond what is already in the schema, so the score is the baseline of 3.

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 'Current sat/vB fee recommendations' clearly states the tool returns recommended fees in satoshis per vbyte. It uses a specific verb ('recommend') and resource ('fees'), and the simplicity distinguishes it from sibling tools like mempool_stats which might offer broader mempool data.

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?

No guidance is provided on when to use this tool versus alternatives such as mempool_stats or other fee-related tools. There is no mention of context, prerequisites, or scenarios where this tool is preferred or should be avoided.

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

All Mempool Space toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources