Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-price

Retrieve current Bitcoin prices across multiple fiat currencies to monitor market values and support financial analysis.

Instructions

Returns the current BTC price in various fiat currencies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the 'get-price' MCP tool with the server, including description and an inline asynchronous handler that calls GeneralService.getPrice() to fetch the price and returns it as formatted text content.
    private registerGetPriceHandler(): void {
      this.server.tool(
        "get-price",
        "Returns the current BTC price in various fiat currencies",
        async () => {
          const text = await this.generalService.getPrice();
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • Helper method in GeneralService that fetches raw price data from the request service and formats it into a user-friendly string using the formatResponse utility.
    async getPrice(): Promise<string> {
      const data = await this.requestService.getPrice();
      return formatResponse<any>("Current Price", data);
    }
  • Core implementation helper that makes the HTTP request to the 'prices' API endpoint via IApiClient to retrieve current BTC price data in various currencies.
    async getPrice(): Promise<any | null> {
      return this.client.makeRequest<any>(`prices`);
    }
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 current prices but lacks details on rate limits, data sources, update frequency, error handling, or response format. This is a significant gap 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 that front-loads the core functionality ('Returns the current BTC price') with no wasted words. It's appropriately sized for a simple tool with no parameters.

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's low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks behavioral details like return format or limitations, which would be helpful for an agent to use it correctly without structured output guidance.

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 with 100% schema description coverage, so the schema fully documents the absence of inputs. The description adds no parameter information, which is appropriate here, earning a baseline score of 4 as it doesn't need to compensate for any gaps.

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 ('current BTC price in various fiat currencies'). It distinguishes from siblings by focusing on price data rather than blockchain transactions, addresses, or blocks, though it doesn't explicitly name the alternative 'get-historical-price' for time-based differentiation.

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 'get-historical-price' for historical data or other siblings for different data types, nor does it specify prerequisites or exclusions, leaving usage context implied rather than explicit.

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