Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-tx-merkleblock-proof

Retrieve the merkleblock proof for a Bitcoin transaction to verify its inclusion in a block. This tool provides cryptographic proof that a specific transaction exists within the blockchain.

Instructions

Returns the merkleblock proof for a transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
txidYesThe txid to get merkleblock proof for

Implementation Reference

  • The MCP tool handler function that invokes TxService.getTxMerkleblockProof and returns formatted text content.
    async ({ txid }) => {
      const text = await this.txService.getTxMerkleblockProof({ txid });
      return { content: [{ type: "text", text }] };
    }
  • Zod schema defining the input parameter 'txid' for the tool.
    {
      txid: z.string().length(64).describe("The txid to get merkleblock proof for"),
    },
  • Method that registers the 'get-tx-merkleblock-proof' tool with MCP server, including description, schema, and handler.
    private registerGetTxMerkleblockProofHandler(): void {
      this.server.tool(
        "get-tx-merkleblock-proof",
        "Returns the merkleblock proof for a transaction",
        {
          txid: z.string().length(64).describe("The txid to get merkleblock proof for"),
        },
        async ({ txid }) => {
          const text = await this.txService.getTxMerkleblockProof({ txid });
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • TxService helper method that fetches the proof from request service and formats it.
    async getTxMerkleblockProof({ txid }: { txid: string }): Promise<string> {
      const data = await this.requestService.getTxMerkleblockProof({ txid });
      return `Transaction Merkleblock Proof: ${data}`;
    }
  • Request service helper that performs the actual API call to retrieve the merkleblock proof.
    async getTxMerkleblockProof({ txid }: { txid: string }): Promise<string | null> {
      return this.client.makeRequest<string>(`tx/${txid}/merkleblock-proof`);
    }
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 data, implying a read-only operation, but lacks details on permissions, rate limits, error conditions, or the format of the returned proof. This is a significant gap for a tool with no 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 directly states the tool's function without unnecessary words. It is front-loaded and wastes no space, 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.

Completeness2/5

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

Given the complexity of blockchain operations and the lack of annotations and output schema, the description is incomplete. It does not explain what a merkleblock proof is, its format, or how it might be used, leaving gaps in understanding for an AI agent. This is inadequate for a tool in a technical domain with many siblings.

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 'txid' parameter well-documented in the schema. The description does not add any meaning beyond the schema, such as explaining what a merkleblock proof entails or constraints on the txid. Baseline score of 3 is appropriate as the schema handles parameter documentation adequately.

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 ('merkleblock proof for a transaction'), making the purpose specific and understandable. However, it does not explicitly differentiate this tool from its many siblings (e.g., get-tx-info, get-tx-raw) beyond the unique 'merkleblock proof' aspect, which is implied but not contrasted.

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 many sibling tools like get-tx-info or get-tx-raw, there is no indication of the specific use case for a merkleblock proof, such as verification contexts or prerequisites, leaving the agent without contextual 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