Agent Data Tools

by io.github.Nutshell2000

Bitcoin fee rates and mempool status: Bitcoin fee estimate in sat/vB for the next block, half hour and hour, with mempool size

btc_fees

Read-only

Current Bitcoin network fee rates in sat/vB for next-block, half-hour, one-hour and economy confirmation, the estimated cost in sats of a typical payment, mempool size and total pending fees, and the latest block height. Use before sending a Bitcoin transaction or to decide whether to wait for lower fees. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Input Schema

Name	Required	Description	Default
`only`	No	Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result

Output Schema

Name	Required	Description
`fees`	Yes
`unit`	Yes
`source`	Yes
`mempool`	Yes
`network`	Yes
`checkedAt`	Yes	Server retrieval time in UTC. Upstream endpoints are not an atomic snapshot.
`blockHeight`	Yes
`limitations`	Yes
`typicalPaymentSats`	Yes
`typicalPaymentVbytes`	Yes	Illustrative transaction-size assumption; not the buyer's transaction size.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / only / description

Previous value: -"Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=fastestFee,halfHourFee); unknown keys are ignored and an empty match returns the full result"New value: +"Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result"

Changed1 schema field changedOct 20, 2026

addedInput schema / properties / only

Added value: +{
+  "description": "Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=fastestFee,halfHourFee); unknown keys are ignored and an empty match returns the full result",
+  "type": "string"
+}

AddedOct 18, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: pricing ($0.002/call via x402 USDC or card key), 25 free calls, failed calls free, and the explicit note that repeats are not free — which explains the non-idempotent hint. It also reaffirms read-only behavior ('reads or computes only and changes nothing').

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?

Front-loads the returned data, then gives usage context, then pricing constraints — a sensible order with no filler. Slightly dense, and the cost/free-tier points are repeated in two sentences, costing a little economy.

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?

With an output schema present, the description needn't document return shape, yet it enumerates the key values (fee tiers, sats cost of a typical payment, mempool size, block height) and covers cost model and safety profile. An agent has everything needed to call and interpret it.

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?

There is one optional parameter (`only`) with 100% schema description coverage, so the schema already explains the comma-separated key filtering and its fallback behavior. The description adds nothing about this parameter, which is acceptable given full coverage but not additive.

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?

States a specific verb+resource: current Bitcoin network fee rates in sat/vB at several confirmation horizons, plus mempool size, pending fees, and block height. The BTC scope cleanly separates it from the many *_gas siblings, which are all EVM-chain gas tools.

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?

Explicitly says to use it 'before sending a Bitcoin transaction or to decide whether to wait for lower fees', which gives a clear decision context. It doesn't name an alternative tool or state when-not to use it, but within this toolset there is no competing BTC fee endpoint to route to.

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

All Agent Data Tools tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.