Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-difficulty-adjustment

Retrieve Bitcoin difficulty adjustment data to understand network mining complexity changes and predict future adjustments.

Instructions

Returns current and next Bitcoin difficulty adjustment info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function for 'get-difficulty-adjustment'. Fetches data from GeneralService and returns it as text content in MCP format.
    async () => {
      const text = await this.generalService.getDifficultyAdjustment();
      return { content: [{ type: "text", text }] };
    }
  • Registers the 'get-difficulty-adjustment' tool with the MCP server, including name, description, and handler function.
    this.server.tool(
      "get-difficulty-adjustment",
      "Returns current and next Bitcoin difficulty adjustment info",
      async () => {
        const text = await this.generalService.getDifficultyAdjustment();
        return { content: [{ type: "text", text }] };
      }
    );
  • Helper method in GeneralService that retrieves raw data from RequestService and formats it into a string response.
    async getDifficultyAdjustment(): Promise<string> {
      const data = await this.requestService.getDifficultyAdjustment();
      return formatResponse<any>("Difficulty Adjustment", data);
    }
  • Core helper method that makes an API request to fetch the difficulty adjustment data.
    async getDifficultyAdjustment(): Promise<any | null> {
      return this.client.makeRequest<any>(`difficulty-adjustment`);
    }
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. It states the tool returns information, implying a read-only operation, but lacks details on rate limits, error conditions, data freshness, or response format. For a tool with zero annotation coverage, this is insufficient to fully inform the agent about its behavior.

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 any unnecessary words. It is front-loaded with the core functionality, 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.

Completeness3/5

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

Given the tool has 0 parameters, 100% schema coverage, and no output schema, the description is minimally adequate. It explains what the tool returns but lacks details on the structure of the difficulty adjustment info (e.g., current vs. next values, units, timestamps), which could be important for an agent to interpret the results correctly. This leaves some gaps in completeness.

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 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, earning a high baseline score as it avoids redundancy. No additional value is required here.

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 tool's purpose with a specific verb ('Returns') and resource ('Bitcoin difficulty adjustment info'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get-stats-info' or 'get-mining-blocks-fees-24h' that might also provide related Bitcoin network data, which prevents a perfect score.

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. It doesn't mention any prerequisites, context for usage, or compare it to sibling tools that might offer overlapping or complementary functionality, 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