Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-block-status

Check Bitcoin block confirmation status by providing a block hash to verify transaction inclusion and network validation.

Instructions

Returns status for a block

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashYesThe block hash to get status for

Implementation Reference

  • Registers the MCP tool 'get-block-status'. Defines input schema requiring a 64-character block hash, description, and handler that delegates to BlocksService.getBlockStatus, returning formatted text content.
    private registerGetBlockStatusHandler(): void {
      this.server.tool(
        "get-block-status",
        "Returns status for a block",
        {
          hash: z.string().length(64).describe("The block hash to get status for"),
        },
        async ({ hash }) => {
          const text = await this.blocksService.getBlockStatus({ hash });
          return { content: [{ type: "text", text }] };
        }
      );
  • BlocksService.getBlockStatus: Fetches block status from request service and formats the IBlockStatusResponse using formatResponse.
    async getBlockStatus({ hash }: IHashParameter): Promise<string> {
      const data = await this.requestService.getBlockStatus({ hash });
      return formatResponse<IBlockStatusResponse>("Block Status", data);
  • Core implementation in BlocksRequestService.getBlockStatus: Makes an API request to the endpoint `block/${hash}/status` using IApiClient.makeRequest.
    async getBlockStatus({ hash }: { hash: string }): Promise<IBlockStatusResponse | null> {
      return this.client.makeRequest<IBlockStatusResponse>(`block/${hash}/status`);
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 'Returns status' but doesn't specify what the return includes (e.g., confirmation count, validity, timestamp), whether it's a read-only operation, or any error conditions. This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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 with the core action, though it could be more informative. The brevity is appropriate but borders on under-specification.

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?

For a tool with no annotations, no output schema, and a vague purpose, the description is incomplete. It doesn't explain what 'status' means, what the return values are, or how it differs from sibling tools. This leaves the agent with insufficient context to use the tool effectively.

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 'hash' parameter documented as 'The block hash to get status for'. The description doesn't add any meaning beyond this, such as hash format examples or constraints. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Returns status for a block' clearly states the verb ('Returns') and resource ('block'), but it's vague about what 'status' entails compared to sibling tools like 'get-block' or 'get-block-header'. It doesn't differentiate itself from similar tools, such as whether 'status' refers to confirmation status, validation status, or other metadata.

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-block' or 'get-block-header'. It doesn't mention any prerequisites, exclusions, or specific contexts, leaving the agent to infer usage from the name alone.

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