Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-address-info

Retrieve Bitcoin address details including transaction history and balance from the blockchain.

Instructions

Returns details about an address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe address to get info for

Implementation Reference

  • Registers the 'get-address-info' MCP tool with server.tool, including description, Zod input schema for 'address', and thin async handler delegating to AddressService.getAddressInfo returning formatted text content.
    private registerGetAddressHandler(): void {
      this.server.tool(
        "get-address-info",
        "Returns details about an address",
        {
          address: z.string().describe("The address to get info for"),
        },
        async ({ address }) => {
          const text = await this.addressService.getAddressInfo({ address });
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • Helper method in AddressService that retrieves address info via requestService and formats the response using formatResponse utility.
    async getAddressInfo({ address }: IAddressParameter): Promise<string> {
      const data = await this.requestService.getAddressInfo({ address });
      return formatResponse<IAddressResponse>("Address Info", data);
    }
  • Core helper that performs the API request to fetch address information from the backend endpoint `address/${address}`.
    async getAddressInfo({ address }: { address: string }): Promise<IAddressResponse | null> {
      return this.client.makeRequest<IAddressResponse>(`address/${address}`);
    }
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 details but doesn't specify what those details include (e.g., balance, transactions, metadata), whether it's read-only, has rate limits, or requires authentication. This lack of context makes it inadequate for a tool with no annotation support.

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 front-loaded and appropriately sized for a simple tool, earning full marks for conciseness.

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 address-related data and the lack of annotations or output schema, the description is incomplete. It doesn't explain what 'details' are returned, leaving the agent uncertain about the tool's behavior and output, which is insufficient for effective use.

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 description doesn't add any meaning beyond the input schema, which has 100% coverage for the single parameter 'address'. Since the schema already fully describes the parameter, the 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 clearly states the tool's purpose with a specific verb ('Returns') and resource ('details about an address'), making it understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-address-txs' or 'get-address-utxo', which might provide transaction or UTXO details instead of general address info.

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 multiple sibling tools related to addresses (e.g., 'get-address-txs', 'get-address-utxo'), it fails to specify what type of 'details' are returned or when this tool is preferred over others, leaving the agent to infer usage.

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