Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-address-utxo

Retrieve unspent transaction outputs (UTXOs) for a Bitcoin address to check available funds and transaction history.

Instructions

Returns UTXOs for an address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe address to get UTXOs for

Implementation Reference

  • Registers the 'get-address-utxo' MCP tool with server, including input schema and execution handler.
    private registerGetAddressUtxoHandler(): void {
      this.server.tool(
        "get-address-utxo",
        "Returns UTXOs for an address",
        {
          address: z.string().describe("The address to get UTXOs for"),
        },
        async ({ address }) => {
          const text = await this.addressService.getAddressUtxo({ address });
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • Core handler implementation: performs the API request to retrieve UTXOs for the address.
    async getAddressUtxo({ address }: { address: string }): Promise<IAddressUtxoResponse[] | null> {
      return this.client.makeRequest<IAddressUtxoResponse[]>(`address/${address}/utxo`);
    }
  • Helper service method that fetches UTXOs and formats the response.
    async getAddressUtxo({ address }: IAddressParameter): Promise<string> {
      const data = await this.requestService.getAddressUtxo({ address });
      return formatResponse<IAddressUtxoResponse[]>("Address UTXOs", data);
    }
  • Type definition for the UTXO response structure used in the tool.
    export interface IAddressUtxoResponse {
      txid: string;
      vout: number;
      value: number;
      status: {
        confirmed: boolean;
        block_height?: number;
        block_hash?: string;
        block_time?: number;
      };
    } 
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 only states what the tool returns without mentioning any behavioral traits such as rate limits, error conditions, or response format. This is inadequate 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 any unnecessary words. It is front-loaded and appropriately sized for its purpose, 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 lack of annotations and output schema, the description is incomplete. It does not explain what UTXOs are, the return format, or any behavioral aspects like pagination or errors. For a tool with no structured support, this leaves significant gaps in 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 input schema has 100% description coverage, with the 'address' parameter fully documented. The description adds no additional semantic information beyond what the schema provides, such as address format or validation rules. 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.

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Returns') and resource ('UTXOs for an address'), making it easy to understand what the tool does. However, it does not explicitly differentiate from sibling tools like 'get-address-info' or 'get-address-txs', which might provide related but different information about addresses.

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-address-info' and 'get-address-txs', there is no indication of how this tool differs or when it is the appropriate choice, leaving usage context unclear.

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