Scored across 12 tools
Each tool targets a distinct action, and descriptions actively disambiguate (backtest_pine vs backtest_pine_grid, transpile-only vs run). The coverage trio (list_coverage_topics → get_coverage_topic → check_pine_feature) is well-nested by granularity, and check_engine_image vs pull_engine_image are clear. Minor overlap: check_tradingview_parity also runs the strategy, and binance_symbols/fetch_binance_ohlcv both touch the Binance API, but boundaries remain legible.
Names consistently use snake_case with a verb_noun pattern (list_*, get_*, check_*, backtest_*, fetch_*, transpile_*, pull_*). The only deviation is binance_symbols, which despite listing/validating omits the list_ prefix. Otherwise highly predictable.
Twelve tools sit squarely in the well-scoped 3-15 range. Each earns its place: core workflow (transpile, backtest, sweep, parity), data/infra (fetch, symbols, image management), and coverage discovery (list/get/check). No filler.
The Pine backtest lifecycle is well covered end-to-end: coverage discovery, transpile, single backtest, parameter sweeps, data fetching, parity verification, and engine/image management. Minor gaps exist, such as no tool to list or retrieve previously generated report_path files or manage saved artifacts, but agents can work around this via filesystem paths.