Skip to main content
Glama
Sign In
Bitcoin Data MCP Server

Bitcoin Data MCP Server

by myownipgit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

analyze_mempool_state

Examine Bitcoin mempool transaction backlog and fees with optional basic predictions for network congestion trends.

Instructions

Analyze current mempool state

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

Input Schema

NameRequiredDescriptionDefault
include_predictionsNoInclude basic predictions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It does not state whether the tool is read-only, what side effects exist, or any authentication requirements. The agent cannot assess safety or impact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise at one sentence, which is positive for brevity, but it lacks essential details that would make it useful. It is more under-specified than efficiently minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one optional param, no output schema), the description should at least indicate the nature of the output or the type of analysis performed. It fails to provide enough context for an agent to understand the tool's capabilities.

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% for the single parameter 'include_predictions', which already has clear description in the schema. The tool description adds no extra context for parameters, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Analyze current mempool state' clearly states the verb and resource, but it does not distinguish from sibling tools like analyze_fee_landscape or analyze_utxo_distribution, which also analyze aspects of the mempool. The purpose is understood but not uniquely defined.

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 vs alternatives. With siblings focusing on specific aspects (fees, UTXO distribution), the description should indicate that this tool provides a general overview or certain predictions.

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

Deploy Server

Other Tools