Skip to main content
Glama
covalenthq

GoldRush MCP Server

by covalenthq

bitcoin_non_hd_wallet_balances

Fetch Bitcoin balance and price data for non-HD wallet addresses. Provides total balance, available funds, transaction count, and spot prices in multiple currencies.

Instructions

Fetch Bitcoin balance for a non-HD address. Response includes spot prices and other metadata. This tool provides detailed balance data for regular Bitcoin addresses. Required: walletAddress - The Bitcoin address to query. Optional: quoteCurrency - The currency for price conversion (USD, EUR, etc). Returns complete balance details including total balance, available balance, and transaction count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletAddressYesThe Bitcoin address to get balance for. Must be a valid non-HD Bitcoin address.
quoteCurrencyNoCurrency to quote Bitcoin values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency.

Implementation Reference

  • The registration and handler implementation for the bitcoin_non_hd_wallet_balances MCP tool.
    server.tool(
        "bitcoin_non_hd_wallet_balances",
        "Fetch Bitcoin balance for a non-HD address. Response includes spot prices and other metadata.\n" +
            "This tool provides detailed balance data for regular Bitcoin addresses.\n" +
            "Required: walletAddress - The Bitcoin address to query.\n" +
            "Optional: quoteCurrency - The currency for price conversion (USD, EUR, etc).\n" +
            "Returns complete balance details including total balance, available balance, and transaction count.",
        {
            walletAddress: z
                .string()
                .describe(
                    "The Bitcoin address to get balance for. Must be a valid non-HD Bitcoin address."
                ),
            quoteCurrency: z
                .enum(Object.values(validQuoteValues) as [string, ...string[]])
                .optional()
                .describe(
                    "Currency to quote Bitcoin values in (e.g., 'USD', 'EUR'). If not specified, uses default quote currency."
                ),
        },
        async (params) => {
            try {
                const response =
                    await goldRushClient.BitcoinService.getBitcoinNonHdWalletBalances(
                        params.walletAddress,
                        {
                            quoteCurrency: params.quoteCurrency as Quote,
                        }
                    );
                return {
                    content: [
                        {
                            type: "text",
                            text: stringifyWithBigInt(response.data),
                        },
                    ],
                };
            } catch (error) {
                return {
                    content: [{ type: "text", text: `Error: ${error}` }],
                    isError: true,
                };
            }
        }
    );
Behavior4/5

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

With no annotations provided, the description carries the full burden and discloses return structure explicitly: 'spot prices', 'total balance', 'available balance', and 'transaction count'. This compensates well for the missing output schema, though it omits rate limits or caching behavior.

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?

The description contains redundant phrasing ('Fetch Bitcoin balance' vs 'provides detailed balance data', 'Response includes' vs 'Returns complete balance details'). While structured logically, it could be tightened by removing repetitive statements about the return data.

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

Completeness4/5

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

Given the simple 2-parameter schema with no nested objects and no output schema, the description adequately completes the picture by enumerating return fields (balance types, transaction count, spot prices). It appropriately addresses the tool's scope without needing to explain complex nested structures.

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 coverage is 100%, establishing a baseline of 3. The description lists parameters as 'Required' and 'Optional' with brief explanations, but largely mirrors the schema descriptions ('Bitcoin address to query' vs schema's 'Bitcoin address to get balance for') without adding significant semantic depth or validation rules.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

Description clearly states 'Fetch Bitcoin balance for a non-HD address' with specific verb (Fetch), resource (Bitcoin balance), and scope (non-HD). The 'non-HD' qualifier effectively distinguishes this tool from the sibling 'bitcoin_hd_wallet_balances'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description specifies 'non-HD address' and 'regular Bitcoin addresses', implying the context for use, but provides no explicit when-to-use guidance or direct reference to the HD wallet alternative. The agent must infer when to select this over 'bitcoin_hd_wallet_balances'.

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