Skip to main content
Glama

Bitview

by io.github.bitcoinresearchkit
OverviewDiscussionsAdmin

Recommended fee rates (precise)

get_precise_fees
Read-onlyIdempotent

Recommended fee rates by confirmation target, with up to three decimal places and support for sub-sat/vB rates.

Mempool.space docs

REST operation: GET /api/v1/fees/precise.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / $defs / FeeRate / format
      Removed value: -"double"
    • addedOutput schema / $defs / PreciseRecommendedFees
      Added value: +{
+  "properties": {
+    "economyFee": {
+      "allOf": [
+        {
+          "$ref": "#/$defs/FeeRate"
+        }
+      ]
+    },
+    "fastestFee": {
+      "allOf": [
+        {
+          "$ref": "#/$defs/FeeRate"
+        }
+      ]
+    },
+    "halfHourFee": {
+      "allOf": [
+        {
+          "$ref": "#/$defs/FeeRate"
+        }
+      ]
+    },
+    "hourFee": {
+      "allOf": [
+        {
+          "$ref": "#/$defs/FeeRate"
+        }
+      ]
+    },
+    "minimumFee": {
+      "allOf": [
+        {
+          "$ref": "#/$defs/FeeRate"
+        }
+      ]
+    }
+  },
+  "required": [
+    "fastestFee",
+    "halfHourFee",
+    "hourFee",
+    "economyFee",
+    "minimumFee"
+  ],
+  "type": "object"
+}
    • removedOutput schema / $defs / RecommendedFees
      Removed value: -{
-  "properties": {
-    "economyFee": {
-      "allOf": [
-        {
-          "$ref": "#/$defs/FeeRate"
-        }
-      ]
-    },
-    "fastestFee": {
-      "allOf": [
-        {
-          "$ref": "#/$defs/FeeRate"
-        }
-      ]
-    },
-    "halfHourFee": {
-      "allOf": [
-        {
-          "$ref": "#/$defs/FeeRate"
-        }
-      ]
-    },
-    "hourFee": {
-      "allOf": [
-        {
-          "$ref": "#/$defs/FeeRate"
-        }
-      ]
-    },
-    "minimumFee": {
-      "allOf": [
-        {
-          "$ref": "#/$defs/FeeRate"
-        }
-      ]
-    }
-  },
-  "required": [
-    "fastestFee",
-    "halfHourFee",
-    "hourFee",
-    "economyFee",
-    "minimumFee"
-  ],
-  "type": "object"
-}
    • changedOutput schema / $ref
      Previous value: -"#/$defs/RecommendedFees"New value: +"#/$defs/PreciseRecommendedFees"
  2. 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 readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description still adds genuinely useful behavior beyond that: output precision (three decimals) and support for sub-sat/vB rates, which materially affects how an agent interprets the returned numbers.

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?

Purpose is front-loaded in the first clause, followed by the distinguishing precision detail. The docs link and REST operation line are compact and aid upstream mapping, though the markdown link is mild boilerplate.

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 parameters, an output schema covering return values, and rich annotations, the description only needs to add units and precision, which it does. A brief note on whether the recommendation is a live mempool estimate or a snapshot would close the remaining gap.

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?

Zero parameters, so the baseline of 4 applies. The phrase 'by confirmation target' usefully signals the shape of the response (rates keyed per target), which is the only semantic an agent needs here.

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 and qualifier (recommended fee rates by confirmation target, with up to three decimal places and sub-sat/vB support), which is far more than a restatement of the name. It stops short of distinguishing this from the adjacent get_block_fee_rates and get_block_fee_rates_precise siblings, so an agent still has to infer why to pick this one.

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 only implied: 'recommended fee rates by confirmation target' hints at the fee-selection use case, but there is no explicit when-to-use, no named alternative, and no statement of when the non-precise or block-based fee endpoints would be preferred.

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

All Bitview 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