Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-stats-info

Retrieve real-time Bitcoin network statistics and blockchain data from the Mempool MCP Server for comprehensive network analysis.

Instructions

Returns stats info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the MCP tool 'get-stats-info'. The provided handler fetches formatted stats info from StatsService and returns it as structured text content.
    private registerGetStatsHandler(): void {
      this.server.tool(
        "get-stats-info",
        "Returns stats info",
        async () => {
          const text = await this.statsService.getStatsInfo();
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • TypeScript interface defining the structure of the stats response data from the API.
    export interface IStatsResponse {
      average_fee: number;
      average_tx_size: number;
      block_count: number;
      mempool_size: number;
      mempool_txs: number;
      total_fees: number;
      total_output: number;
      total_size: number;
      total_weight: number;
    } 
  • Service method that retrieves raw stats data via StatsRequestService and formats it using formatResponse utility.
    async getStatsInfo(): Promise<string> {
      const data = await this.requestService.getStatsInfo();
      return formatResponse<IStatsResponse>("Stats Info", data);
    }
  • Core implementation that makes the HTTP request to the `/stats` API endpoint using IApiClient.
    async getStatsInfo(): Promise<IStatsResponse | null> {
      return this.client.makeRequest<IStatsResponse>(`stats`);
    }
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Returns stats info' only indicates a read operation but fails to describe what the stats include, format, potential rate limits, authentication needs, or any side effects. This is inadequate for a tool with zero annotation coverage.

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 extremely concise ('Returns stats info'), which could be efficient if it were informative. However, it's under-specified rather than appropriately concise, as it lacks necessary details. It's front-loaded but fails to provide value in its brevity.

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

Completeness1/5

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

Given the complexity implied by sibling tools (e.g., various blockchain data tools), no annotations, no output schema, and a vague description, this is highly incomplete. The description doesn't clarify what 'stats info' entails, making it insufficient for effective tool selection and invocation.

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 input schema has 0 parameters with 100% coverage, meaning no parameters need documentation. The description doesn't add parameter details, which is acceptable here as there are none to explain. A baseline of 4 is appropriate for zero-parameter tools.

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

Purpose2/5

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

The description 'Returns stats info' is a tautology that essentially restates the tool name 'get-stats-info' without adding meaningful specificity. It doesn't specify what kind of stats (blockchain statistics, network statistics, etc.) or what resource these stats pertain to, making it vague and minimally informative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its many siblings (e.g., get-mempool-info, get-difficulty-adjustment, get-mining-pools). There is no mention of context, prerequisites, or alternatives, leaving the agent with no usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexandresanlim/mempool-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server