Skip to main content
Glama
covalenthq

GoldRush MCP Server

by covalenthq

bitcoin_transactions

Fetch the complete transaction history for any Bitcoin wallet address, including timestamps, amounts, and transaction IDs, with pagination support.

Instructions

Used to fetch the full transaction history of a Bitcoin wallet. Required: address - The Bitcoin address to query transactions for. Optional: pageSize - Number of results per page (default: 10). Optional: pageNumber - Page number for pagination (default: 0, first page). Returns comprehensive transaction details including timestamps, amounts, and transaction IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe Bitcoin address to get transaction history for. Must be a valid Bitcoin address.
pageSizeNoNumber of transactions to return per page. Default is 10, maximum is 100.
pageNumberNoPage number for pagination, starting from 0. Default is 0.

Implementation Reference

  • Implementation of the "bitcoin_transactions" tool, including registration, input schema definition, and the handler function.
    server.tool(
        "bitcoin_transactions",
        "Used to fetch the full transaction history of a Bitcoin wallet.\n" +
            "Required: address - The Bitcoin address to query transactions for.\n" +
            "Optional: pageSize - Number of results per page (default: 10).\n" +
            "Optional: pageNumber - Page number for pagination (default: 0, first page).\n" +
            "Returns comprehensive transaction details including timestamps, amounts, and transaction IDs.",
        {
            address: z
                .string()
                .describe(
                    "The Bitcoin address to get transaction history for. Must be a valid Bitcoin address."
                ),
            pageSize: z
                .number()
                .optional()
                .default(10)
                .describe(
                    "Number of transactions to return per page. Default is 10, maximum is 100."
                ),
            pageNumber: z
                .number()
                .optional()
                .default(0)
                .describe(
                    "Page number for pagination, starting from 0. Default is 0."
                ),
        },
        async (params) => {
            try {
                const response =
                    await goldRushClient.BitcoinService.getTransactionsForBtcAddress(
                        {
                            address: params.address,
                            pageSize: params.pageSize,
                            pageNumber: params.pageNumber,
                        }
                    );
                return {
                    content: [
                        {
                            type: "text",
                            text: stringifyWithBigInt(response.data),
                        },
                    ],
                };
            } catch (error) {
                return {
                    content: [{ type: "text", text: `Error: ${error}` }],
                    isError: true,
                };
            }
        }
    );
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses return values ('timestamps, amounts, and transaction IDs') and pagination defaults, but omits safety characteristics (read-only vs destructive), rate limits, or error behaviors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Inefficiently repeats parameter specifications that are already fully documented in the input schema. The return value description is useful, but the parameter listing wastes space that could elaborate on Bitcoin-specific behaviors.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a query tool with three simple parameters. Compensates somewhat for missing output schema by describing return contents. However, lacks Bitcoin-specific context (e.g., confirmation requirements, support for different address formats like SegWit).

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%, establishing baseline 3. The description repeats parameter definitions already present in the schema without adding syntactic guidance or semantic nuances (e.g., it omits the 'maximum is 100' constraint for pageSize present in the schema).

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?

Clearly states it 'fetch[es] the full transaction history of a Bitcoin wallet' with specific verb and resource. Distinguishes from multichain siblings by specifying 'Bitcoin,' but does not differentiate from the similarly-named sibling 'transactions_for_address'.

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?

Provides no guidance on when to use this tool versus siblings like 'transactions_for_address' or 'multichain_transactions'. No mention of prerequisites (e.g., address format validation) or when pagination is necessary.

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/covalenthq/goldrush-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server