Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-mining-pools

Retrieve Bitcoin mining pool data to analyze network distribution and identify major participants in block production.

Instructions

Returns mining pools info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the 'get-mining-pools' MCP tool, including the inline handler function that delegates to MiningService.getMiningPools() and formats the response as text content.
    private registerGetMiningPoolsHandler(): void {
      this.server.tool(
        "get-mining-pools",
        "Returns mining pools info",
        async () => {
          const text = await this.miningService.getMiningPools();
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • Helper method in MiningService that fetches mining pools data via RequestService and formats it using formatResponse.
    async getMiningPools(): Promise<string> {
      const data = await this.requestService.getMiningPools();
      return formatResponse<IMiningPoolsResponse[]>("Mining Pools", data);
    }
  • Core helper that performs the actual API request to retrieve mining pools data.
    async getMiningPools(): Promise<IMiningPoolsResponse[] | null> {
      return this.client.makeRequest<IMiningPoolsResponse[]>(`mining/pools`);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Returns mining pools info' implies a read-only operation but doesn't disclose behavioral traits such as rate limits, authentication needs, data freshness, or response format. 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.

Conciseness5/5

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

The description is a single, efficient sentence with no wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'mining pools info' includes (e.g., list of pools, statistics, or details), making it hard for an agent to understand the tool's full behavior and output.

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, so no parameter documentation is needed. The description doesn't add parameter details, which is acceptable here, but it could have mentioned if any implicit parameters (e.g., network context) are required, keeping it from a perfect score.

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?

The description 'Returns mining pools info' clearly states the verb ('Returns') and resource ('mining pools info'), making the purpose understandable. However, it doesn't differentiate from the sibling tool 'get-mining-pool' (singular vs. plural), which could cause confusion about when to use each tool.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get-mining-pool' or other mining-related tools. It lacks context about whether this returns all pools, specific pools, or aggregated data, leaving usage unclear.

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