Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-address-txs-chain

Retrieve Bitcoin blockchain transaction history for a specific address to analyze past activity and verify on-chain transfers.

Instructions

Returns chain transactions for an address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe address to get chain txs for

Implementation Reference

  • MCP tool handler registration for 'get-address-txs-chain', including input schema (address: string) and execution logic that delegates to AddressService.getAddressTxsChain and returns MCP-formatted response.
    private registerGetAddressTxsChainHandler(): void {
      this.server.tool(
        "get-address-txs-chain",
        "Returns chain transactions for an address",
        {
          address: z.string().describe("The address to get chain txs for"),
        },
        async ({ address }) => {
          const text = await this.addressService.getAddressTxsChain({ address });
          return { content: [{ type: "text", text }] };
        }
      );
  • Helper method in AddressService that fetches chain transactions via request service and formats the response.
    async getAddressTxsChain({ address }: IAddressParameter): Promise<string> {
      const data = await this.requestService.getAddressTxsChain({ address });
      return formatResponse<IAddressTxResponse[]>(
        "Address Chain Transactions",
        data
      );
    }
  • Core helper implementation: performs API request to retrieve chain transactions for the address.
    async getAddressTxsChain({ address }: { address: string }): Promise<IAddressTxResponse[] | null> {
      return this.client.makeRequest<IAddressTxResponse[]>(`address/${address}/txs/chain`);
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states it 'returns' data, implying a read-only operation, but doesn't disclose behavioral traits such as rate limits, authentication needs, pagination, or what 'chain transactions' entails (e.g., format, time range, or completeness). 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 with zero waste. It's appropriately sized and front-loaded, clearly stating the tool's function without unnecessary elaboration, earning a high score 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 no annotations, no output schema, and a simple parameter schema, the description is incomplete. It doesn't explain what 'chain transactions' returns, how results are structured, or any limitations, making it insufficient for an agent to fully understand the tool's behavior and output.

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 adds minimal meaning beyond the input schema, which has 100% coverage for the single parameter 'address'. It implies the parameter is used to fetch transactions, but doesn't specify address format or constraints. With high schema coverage, the baseline is 3, as the schema already documents the parameter 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 verb ('returns') and resource ('chain transactions for an address'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get-address-txs' or 'get-address-txs-mempool', which likely return different types of transaction data, so it lacks specific 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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get-address-txs' and 'get-address-txs-mempool', it's unclear what 'chain transactions' specifically refers to (e.g., confirmed vs. unconfirmed, blockchain-specific), leaving the agent without usage 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