Scored across 12 tools
Most tools have clearly distinct purposes: transpile vs. backtest vs. sweep vs. parity-check are unambiguous, and backtest_pine is explicitly contrasted with backtest_pine_grid. The coverage trio (list_coverage_topics, get_coverage_topic, check_pine_feature) is separated by granularity but still overlaps in the 'does PineForge support X?' space, and pull_engine_image/check_engine_image overlap slightly since check can auto_pull.
All names are snake_case, mostly following a verb_noun pattern (check_tradingview_parity, transpile_pine, backtest_pine, fetch_binance_ohlcv, list_coverage_topics, get_coverage_topic, pull_engine_image). The only real deviation is binance_symbols, which is noun-only with no verb, but grouping is otherwise predictable.
12 tools is well-scoped for a Pine transpile/backtest/parity server, with each tool earning its place across transpilation, execution, sweeps, data fetching, coverage discovery, and engine management. No redundant or filler tools.
The surface covers the full workflow: find/validate symbols, fetch data, check coverage, transpile, backtest, sweep, and verify TradingView parity, plus engine image management. Minor gaps exist (no way to cancel/abort a long backtest or directly ingest TradingView exports beyond parity-check inputs), but core lifecycle is complete.