Bitcoin Intelligence for AI Agents. Provides 10 tools for Bitcoin ecosystem data including price, mempool, fees, blocks, addresses, transactions, network stats, Lightning Network, Ordinals/Inscriptions, and whale alerts.
btcOracle has 10 tools with basic descriptions and no input schemas visible in the provided code. All tools are READ_ONLY and stateless, which is good. However, critical gaps exist: (1) No input schema definitions shown for any tool, only parameter names and types are listed in the spec, not in actual JSON Schema format in the code. (2) Descriptions are present but generic (avg ~80 chars), lacking LLM-optimized guidance on WHEN to use each tool vs. similar ones. (3) No output schemas documented, agents cannot plan downstream calls. (4) No error handling guidance visible. (5) Tool names follow verb_noun pattern (btc_*) but lack clarity on distinctions (e.g., btc_address_check vs btc_tx_lookup overlap in intent). Per-tool scores average 52 due to missing schemas and weak descriptions.
Address balance, TX count, received/spent.
Latest block info, hashrate, difficulty, halving countdown.
Real-time fee tracker with USD cost estimates for common TX types.
Ordinals inscription lookup, BRC-20 tokens.
Lightning Network capacity, nodes, channels.
Mempool depth, fee recommendations, congestion level, pending TX count.
Node count, hashrate trend, difficulty adjustment.
No input schemas visible in source code. Tools with parameters (btc_address_check, btc_tx_lookup, btc_inscription, btc_whale_alert) show parameter names and types in spec but no JSON Schema definitions in server.py. Cannot verify type constraints, required fields, or format patterns.
No output schemas documented. Handlers return dicts (e.g., handle_overview returns nested dict with price, dominance, network, supply) but no schema is declared for agents to understand structure. Agents cannot plan downstream calls or extract fields reliably.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | <=2025-11-25 | v2 |
Bitcoin ecosystem overview: price, market cap, dominance, supply stats.
TX status, confirmations, inputs/outputs, fee.
Large transactions > threshold BTC in recent blocks.
Descriptions are generic and lack LLM-optimized guidance. E.g., 'Bitcoin ecosystem overview: price, market cap, dominance, supply stats.' (80 chars) does not explain WHEN to call this vs btc_block_stats or btc_network_stats. No dependency hints or prerequisites stated.
No error handling guidance visible. Code catches exceptions and returns {'error': str(e)[:80]} but does not categorize errors as retryable, user-fixable, or fatal. Agents cannot determine next steps on failure.
Parameter descriptions missing or minimal. btc_address_check has 'Bitcoin address to check' (27 chars), does not specify format (P2PKH, P2SH, Bech32), length, or validation rules. btc_whale_alert threshold_btc lacks min/max bounds.