Skip to main content
Glama

A Bitcoin mainnet address: confirmed and unconfirmed

btc_address
Read-only

A Bitcoin mainnet address: confirmed and unconfirmed balance in BTC and USD, transaction count, funded and spent totals, and its last 10 transactions with the net change for the address. Mainnet bech32 and legacy addresses only. Source: mempool.space. Information only, not financial advice. Related tools on this server, for a different need: btc_fees when you need Recommended Bitcoin fees in sat/vB, the mempool's size; btc_tx when you need to check a Bitcoin transaction's status, fee and size. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "btc_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesBitcoin mainnet address (bc1…, 1… or 3…)

Output Schema

NameRequiredDescriptionDefault
btcUsdNo
sourceNo
totalsNo
addressNo
balanceNo
checkedAtNo
disclaimerNo
recentTransactionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantive behavior beyond them: the upstream source (mempool.space), the fixed scope of 10 transactions, the billing model ($0.002 per successful call via x402, failed calls not charged), and an informational disclaimer. Pricing and source disclosure are exactly what annotations cannot convey.

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

Conciseness4/5

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

The payload summary is front-loaded and the sibling routing is compact. The payment boilerplate and "Information only, not financial advice" line are functional but add length that could be trimmed without loss of agent-relevant meaning.

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

Completeness5/5

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

The tool has an output schema, so return-field semantics are already covered; the description fills the remaining gaps an agent needs — address network constraint, data source, transaction-count scope, and cost. Nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter's format (bc1…, 1…, 3…) is already documented in the schema. The description adds one genuine constraint beyond it — mainnet only, implying testnet addresses are rejected — but does not elaborate further, so it sits just above the baseline.

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?

The description names the resource (a Bitcoin mainnet address) and enumerates the exact payload: confirmed/unconfirmed balance in BTC and USD, tx count, funded/spent totals, and the last 10 transactions with net change. It also distinguishes itself from siblings by naming btc_fees and btc_tx with their own purposes.

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

Usage Guidelines5/5

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

It states an explicit acceptance constraint ("Mainnet bech32 and legacy addresses only") and routes the agent to alternatives with conditions: btc_fees for recommended fees and mempool size, btc_tx for a single transaction's status/fee/size. That is when-to-use, when-not, and named alternatives in one place.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources