Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-tx-raw

Retrieve the raw hexadecimal data for any Bitcoin transaction by providing its transaction ID (txid). This tool enables developers to access complete transaction details directly from the Bitcoin blockchain for analysis, verification, or integration purposes.

Instructions

Returns raw hex for a transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
txidYesThe txid to get raw hex for

Implementation Reference

  • Registration of the MCP tool 'get-tx-raw', including input schema (txid: string length 64) and handler that delegates to TxService.getTxRaw and formats response
    private registerGetTxRawHandler(): void {
      this.server.tool(
        "get-tx-raw",
        "Returns raw hex for a transaction",
        {
          txid: z.string().length(64).describe("The txid to get raw hex for"),
        },
        async ({ txid }) => {
          const text = await this.txService.getTxRaw({ txid });
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • TxService.getTxRaw method: fetches raw tx from request service and prefixes with 'Transaction Raw Hex: '
    async getTxRaw({ txid }: { txid: string }): Promise<string> {
      const data = await this.requestService.getTxRaw({ txid });
      return `Transaction Raw Hex: ${data}`;
    }
  • TxRequestService.getTxRaw: makes API request to `/tx/{txid}/raw` endpoint to retrieve raw transaction hex
    async getTxRaw({ txid }: { txid: string }): Promise<string | null> {
      return this.client.makeRequest<string>(`tx/${txid}/raw`);
    }
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 action ('Returns raw hex') but doesn't mention potential constraints like rate limits, error conditions, or what 'raw hex' entails (e.g., format, encoding). 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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 transaction data tools and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'raw hex' means in practice, potential use cases, or how it differs from other transaction-related tools, leaving the agent with insufficient context for optimal tool selection.

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?

Schema description coverage is 100%, with the parameter 'txid' well-documented in the schema as 'The txid to get raw hex for'. The description adds no additional meaning beyond this, so it meets the baseline for high schema coverage without compensating further.

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 resource ('raw hex for a transaction'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'get-tx-info' or 'get-block-raw', which might provide related transaction data but in different formats or contexts, leaving room for improvement in sibling 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 many sibling tools available (e.g., 'get-tx-info', 'get-tx-status'), there's no indication of when raw hex is preferred over other transaction data, leaving the agent to guess based on context.

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