Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-tx-outspend

Check if a Bitcoin transaction output has been spent by querying its spending transaction details using transaction ID and output index.

Instructions

Returns outspend info for a transaction output

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
txidYesThe txid to get outspend for
voutYesThe vout index to get outspend for

Implementation Reference

  • Registers the MCP tool 'get-tx-outspend' with server.tool, including tool name, description, Zod input schema (txid, vout), and async handler that delegates to TxService.getTxOutspend and returns MCP-formatted text content.
    private registerGetTxOutspendHandler(): void {
      this.server.tool(
        "get-tx-outspend",
        "Returns outspend info for a transaction output",
        {
          txid: z.string().length(64).describe("The txid to get outspend for"),
          vout: z.number().int().describe("The vout index to get outspend for"),
        },
        async ({ txid, vout }) => {
          const text = await this.txService.getTxOutspend({ txid, vout });
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • Application service method getTxOutspend that calls the infrastructure request service and formats the response for the tool handler.
    async getTxOutspend({
      txid,
      vout,
    }: {
      txid: string;
      vout: number;
    }): Promise<string> {
      const data = await this.requestService.getTxOutspend({ txid, vout });
      return formatResponse<any>("Transaction Outspend", data);
    }
  • Infrastructure service method that makes the actual API request to fetch outspend data for the given txid and vout via IApiClient.
    async getTxOutspend({ txid, vout }: { txid: string; vout: number }): Promise<any | null> {
      return this.client.makeRequest<any>(`tx/${txid}/outspend/${vout}`);
    }
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 what the tool does but lacks details on permissions, rate limits, error handling, or what 'outspend info' entails. 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's appropriately sized and front-loaded, with zero waste.

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 a blockchain tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'outspend info' includes, potential errors, or behavioral traits, making it inadequate for full agent understanding.

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 schema description coverage is 100%, with clear descriptions for both parameters (txid and vout). The description doesn't add any meaning beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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 ('outspend info for a transaction output'), making the purpose understandable. However, it doesn't explicitly differentiate from its sibling 'get-tx-outspends', which likely returns multiple outspends, so it misses full sibling distinction.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention any context, prerequisites, or exclusions, leaving the agent to infer usage from the tool 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