Related Servers

There are many overlapping tools: get_address_transactions vs get_address_history vs get_indexed_transaction; analyze_transaction vs get_indexed_transaction vs decode_raw_transaction; get_market_sentiment vs get_btc_price; multiple fee tools (get_fee_estimates, get_fee_recommendation, estimate_smart_fee, compare_fee_estimates, estimate_transaction_cost); multiple mempool tools (analyze_mempool, get_mempool_info) and repeated node-info tools. Descriptions help somewhat, but the boundaries between several tools are blurry enough that an agent will frequently misselect.

Nearly all tools use a consistent verb_noun or snake_case pattern (get_, analyze_, decode_, send_, estimate_). A few like analyze_next_block, search_blockchain, and describe_rpc_command are slightly less conventional but still readable. No camelCase mixing or chaotic styles.

50 tools is far too many for a single Bitcoin utility server; the surface sprawls across RPC access, fee estimation, mempool analysis, mining, address tools, PSBT security, and Lightning decoding. Several near-duplicate tools exist that could be consolidated, suggesting an overloaded rather than well-scoped set.

The domain coverage is broad and there are few obvious dead ends: block, transaction, mempool, fee, mining, address, supply, and PSBT tooling are all present. Some gaps remain (e.g., no explicit wallet/transaction-construction or tracked-address registration flow), but core workflows are covered.