Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-mempool-info

Retrieve real-time Bitcoin mempool data to monitor transaction status and network activity for blockchain analysis.

Instructions

Returns mempool info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the 'get-mempool-info' tool on the MCP server with a handler that calls MempoolService to get info and returns formatted text content.
    private registerGetMempoolHandler(): void {
      this.server.tool(
        "get-mempool-info",
        "Returns mempool info",
        async () => {
          const text = await this.mempoolService.getMempoolInfo();
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • Inline handler function for the 'get-mempool-info' tool that delegates to service and structures MCP response.
    async () => {
      const text = await this.mempoolService.getMempoolInfo();
      return { content: [{ type: "text", text }] };
    }
  • TypeScript interface defining the structure of mempool info response data used by the tool.
    export interface IMempoolInfoResponse {
      count: number;
      vsize: number;
      total_fee: number;
    }
  • Application service method that fetches raw mempool info and formats it for the tool response.
    async getMempoolInfo(): Promise<string> {
      const data = await this.requestService.getMempoolInfo();
      return formatResponse<IMempoolInfoResponse>("Mempool Info", data);
    }
  • Infrastructure service method performing the HTTP request to the mempool API endpoint.
    async getMempoolInfo(): Promise<IMempoolInfoResponse | null> {
      return this.client.makeRequest<IMempoolInfoResponse>(`mempool`);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal insight. It implies a read-only operation ('Returns'), but lacks details on rate limits, error conditions, or the format of returned data. This is inadequate for a tool with zero parameter complexity.

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?

The description is extremely concise with a single, straightforward sentence. It is front-loaded and wastes no words, making it efficient for an agent to parse, though this conciseness comes at the cost of detail.

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 (0 parameters, no output schema, no annotations), the description is incomplete. It fails to explain what 'mempool info' includes, how it differs from sibling mempool tools, or behavioral traits like response format, leaving significant gaps for agent understanding.

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 has zero parameters, and the input schema has 100% description coverage, so no parameter documentation is needed. The description does not add parameter semantics, but this is acceptable given the lack of parameters, warranting a baseline score above minimum.

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 mempool info' is a tautology that merely restates the tool name 'get-mempool-info' without adding meaningful specificity. It lacks a clear verb-resource combination or details about what 'mempool info' entails, though it correctly identifies the resource as 'mempool'.

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 versus alternatives. While sibling tools like 'get-mempool-recent' and 'get-mempool-txids' exist for related mempool queries, the description offers no context, prerequisites, or distinctions to help an agent choose appropriately.

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