Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-block-txids

Retrieve transaction IDs for a specific Bitcoin block by providing its hash. This tool accesses blockchain data to list all transaction identifiers within a given block.

Instructions

Returns txids for a block

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashYesThe block hash to get txids for

Implementation Reference

  • Registers the 'get-block-txids' MCP tool, including description, input schema (hash: 64-char string), and handler that delegates to BlocksService and formats response as text.
    private registerGetBlockTxidsHandler(): void {
      this.server.tool(
        "get-block-txids",
        "Returns txids for a block",
        {
          hash: z.string().length(64).describe("The block hash to get txids for"),
        },
        async ({ hash }) => {
          const text = await this.blocksService.getBlockTxids({ hash });
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • Application service method that retrieves block txids via request service and formats the response using formatResponse.
    async getBlockTxids({ hash }: IHashParameter): Promise<string> {
      const data = await this.requestService.getBlockTxids({ hash });
      return formatResponse<IBlockTxidsResponse[]>("Block Txids", data);
    }
  • Infrastructure service method implementing the core logic: API request to `/block/{hash}/txids` via IApiClient.
    async getBlockTxids({ hash }: { hash: string }): Promise<IBlockTxidsResponse[] | null> {
      return this.client.makeRequest<IBlockTxidsResponse[]>(`block/${hash}/txids`);
    }
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 txids but doesn't mention any behavioral traits like whether it's read-only, safe to use, has rate limits, or what the output format looks like. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 extremely concise with a single sentence that directly states the tool's function. It's front-loaded and wastes no words, making it easy to parse quickly without unnecessary detail.

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 for a tool that likely returns a list of transaction IDs. It doesn't explain the return type, format, or any error conditions, which are crucial for an AI agent to use it correctly. The high schema coverage helps with inputs, but overall context is lacking.

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 fully documented. The description doesn't add any meaning beyond what the schema provides, such as explaining the hash format or constraints. Given the high schema coverage, a baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 'Returns txids for a block' clearly states the action (returns) and resource (txids for a block), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'get-block-txs' or 'get-block-txid-by-index', which appear to serve similar block-related functions, so it doesn't achieve full 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. With sibling tools such as 'get-block-txs' and 'get-block-txid-by-index' that likely handle block transactions, there's no indication of what makes this tool unique or when it should be preferred, leaving usage ambiguous.

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