Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-mining-pool

Retrieve detailed information about a specific Bitcoin mining pool by providing its pool ID, enabling analysis of pool performance and network contributions.

Instructions

Returns info for a specific mining pool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
poolIdYesThe poolId to get info for

Implementation Reference

  • The MCP tool handler function for "get-mining-pool". It takes poolId, fetches data from MiningService.getMiningPool, and returns a text content response.
    async ({ poolId }) => {
      const text = await this.miningService.getMiningPool({ poolId });
      return { content: [{ type: "text", text }] };
    }
  • Input schema for the "get-mining-pool" tool, defining the required 'poolId' string parameter using Zod.
    {
      poolId: z.string().describe("The poolId to get info for"),
    },
  • Registration of the "get-mining-pool" MCP tool, including name, description, input schema, and handler function.
    private registerGetMiningPoolHandler(): void {
      this.server.tool(
        "get-mining-pool",
        "Returns info for a specific mining pool",
        {
          poolId: z.string().describe("The poolId to get info for"),
        },
        async ({ poolId }) => {
          const text = await this.miningService.getMiningPool({ poolId });
          return { content: [{ type: "text", text }] };
        }
      );
  • Helper method in MiningService that retrieves mining pool data from the request service and formats it as a string.
    async getMiningPool({ poolId }: { poolId: string }): Promise<string> {
      const data = await this.requestService.getMiningPool({ poolId });
      return formatResponse<IMiningPoolResponse>("Mining Pool", data);
    }
  • Core helper that performs the actual API request to fetch the specific mining pool data using the API client.
    async getMiningPool({ poolId }: { poolId: string }): Promise<IMiningPoolResponse | null> {
      return this.client.makeRequest<IMiningPoolResponse>(`mining/pool/${poolId}`);
    }
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 of behavioral disclosure. It states the tool returns info but does not describe the return format, error handling, rate limits, or authentication needs. This leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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 that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured for quick understanding.

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 does not explain what 'info' includes, potential errors, or how results are structured. For a tool with no structured behavioral data, the description should provide more context to be fully helpful.

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?

The input schema has 100% description coverage, with the 'poolId' parameter fully documented. The description adds no additional meaning beyond the schema, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

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 clearly states the verb ('Returns') and resource ('info for a specific mining pool'), making the purpose understandable. However, it does not differentiate from sibling tools like 'get-mining-pools' (which likely returns multiple pools), leaving room for ambiguity in distinguishing between them.

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, such as 'get-mining-pools' for listing multiple pools or other mining-related tools. It lacks explicit context or exclusions, offering minimal 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