SiteCheck Crypto & Finance

Bitcoin mempool pressure state and projected next blocks

crypto_btc_mempool_pressure

Read-only

Bitcoin mempool pressure state and projected next blocks. Class (low/normal/high/extreme) is determined deterministically: extreme if next block median fee >= 50 sat/vB or backlog >= 150 vMB; high if >= 20 sat/vB or >= 60 vMB; normal if >= 3 sat/vB or >= 10 vMB; low otherwise. Related tools on this server, for a different need: crypto_btc_blocks_range when you need up to 144 consecutive Bitcoin blocks descending; crypto_btc_chain_tips when you need recent stale/orphaned Bitcoin blocks and sidechain forks. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
`maxBlocks`	No	Maximum projected blocks to return (1-10, default 8)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the deterministic classification thresholds (sat/vB and vMB cutoffs for extreme/high/normal/low), so the agent knows the output is rule-based rather than opaque. It also discloses payment mechanics ($0.002 USDC via x402 on Base/Solana/Arc) and that failed calls are not charged, which is important cost/auth behavior for an openWorld tool.

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 purpose, then the classification rule, then sibling routing, then pricing - a sensible order. The threshold sentences are dense but each carries decision-relevant information. The sibling-routing sentence is slightly verbose relative to its value.

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?

An output schema exists, so return-value details need not be spelled out, and annotations already cover read-only/open-world traits. With one optional parameter at full coverage, purpose, deterministic logic, sibling routing and pricing are all present. Minor gap: it does not clarify what a 'projected block' contains (fee bands, tx counts) beyond the schema.

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?

Schema description coverage is 100% and the single optional maxBlocks parameter is fully documented in-schema (1-10, default 8). The description adds no further meaning about the parameter, so the baseline of 3 applies.

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?

Names a specific resource and output: Bitcoin mempool pressure state (low/normal/high/extreme) plus projected next blocks. It distinguishes itself from two siblings explicitly. However, it does not differentiate from the very close siblings crypto_bitcoin_mempool_stats and crypto_btc_fee_curve, leaving ambiguity about which mempool view to pick.

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 routes the agent away for two cases ('when you need up to 144 consecutive blocks descending' -> crypto_btc_blocks_range; 'recent stale/orphaned blocks and sidechain forks' -> crypto_btc_chain_tips), which is real when-to-use guidance. It stops short of stating when this tool should be preferred over crypto_bitcoin_mempool_stats or crypto_btc_fee_curve.

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

All SiteCheck Crypto & Finance tools Inspect

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

Need Help?