Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

btc-mempool

[x402 paid: $0.005 USDC on Base] BTC mempool: recommended fee rates (sat/vB) + pending tx count (mempool.space). tools/call returns the live payment challenge.

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": "btc-mempool"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the x402 paid model, the exact price ($0.005 USDC on Base), and the critical behavioral quirk that the first tools/call returns a live payment challenge rather than data. It does not cover rate limits or whether fee output is a single rate or multiple priority tiers, which keeps it short of a 5.

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 compact clauses: payment terms front-loaded in a bracket, then resource, output shape, and data source, ending with the payment-challenge behavior. No filler sentences and nothing an agent needs is buried.

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?

No output schema exists, so the description must state the return shape, which it does (fee rates in sat/vB plus pending tx count). For a parameterless, paid read tool this is nearly sufficient; only the granularity of the fee recommendations and response format are left unstated.

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 the baseline is 4 and there is nothing for the description to disambiguate. The description correctly adds no parameter noise and instead spends its words on payment and output semantics.

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 (BTC mempool) and exactly what is returned: recommended fee rates in sat/vB plus pending transaction count, with the upstream source (mempool.space). It is unambiguous about what the tool does, though it does not explicitly contrast with chain-specific siblings like eth-gas or base-gas.

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: an agent can infer it should call this when it needs Bitcoin fee estimates or mempool congestion. There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternative fee/chain tools, though the chain scope ('BTC') implicitly separates it from the ETH/Base gas tools.

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.

Resources