Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-base-url

Retrieve the base API URL for accessing Bitcoin mempool data through the Mempool MCP Server, enabling AI clients to query real-time blockchain information.

Instructions

Returns mempool.space base url api

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the 'get-base-url' MCP tool with server.tool(), providing description and an inline async handler that fetches the base URL from HelpService and formats the response.
    private registerGetBaseURL(): void {
      this.server.tool(
        "get-base-url",
        "Returns mempool.space base url api",
        async () => {
          const text = await this.service.getBaseUrl();
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • Core helper method in HelpService that returns the formatted base URL string, which is used by the tool's handler.
    async getBaseUrl(): Promise<string> {
      return `base URL: ${this.baseUrl}`;
    }
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 something, but doesn't clarify if it's a read-only operation, whether it requires authentication, has rate limits, or what the output format is. This leaves significant gaps in understanding how the tool behaves.

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 what the tool does without any fluff. It's front-loaded with the core purpose, making it easy to parse quickly. Every word earns its place.

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 has no parameters and no output schema, the description is incomplete. It doesn't specify what the return value is (e.g., a string, JSON object), which is critical for an AI agent to use it correctly. With no annotations to fill gaps, this leaves too much ambiguity.

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 schema description coverage is 100%, so there's no need for parameter details in the description. The description appropriately doesn't discuss parameters, focusing on the tool's purpose instead. A baseline of 4 is justified as it avoids unnecessary repetition.

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 action ('Returns') and the resource ('mempool.space base url api'), making the purpose understandable. It distinguishes itself from sibling tools by focusing on API metadata rather than blockchain data operations. However, it doesn't specify what exactly is returned (e.g., a string URL, configuration object), keeping it from 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?

No explicit guidance is provided on when to use this tool versus alternatives. The description implies it's for retrieving the base URL, but there's no mention of prerequisites, typical use cases, or how it relates to other tools (e.g., whether it's needed before calling other API endpoints).

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