No user-submitted related servers found.
Scored across 29 tools
Most tools map to distinct resources/actions, but bgi_collect_now and bgi_collect_material both present as 'one-click collect' entries with overlapping trigger-and-watch behavior, and bgi_watch vs bgi_wait_milestone both poll for run phase/completion. The read-only state tools (bgi_status, bgi_doctor, bgi_schedule_info, bgi_watch) are individually described but require reading carefully to pick correctly.
Nearly all tools share a bgi_ prefix followed by verb_noun (list_groups, run_js, create_group, set_config, install_js, collect_material). A few benign deviations exist — bgi_status, bgi_results, bgi_doctor, bgi_watch are noun-only and bgi_log_search inverts the verb/noun order — but the overall convention is clear and predictable.
29 tools is on the heavy side for the domain; while the underlying surface (execution, config editing, repo browsing, installs, diagnostics) is genuinely broad, the count brushes against the point where several read-only/status tools feel redundant. It sits at the uncomfortable edge between justified breadth and over-exposure.
The lifecycle is well covered: status/doctor diagnostics, game start, multiple run modes, milestone/verdict polling, results and log search, config read/write, group and one-dragon creation, script install, and close. Gaps are minor — there is no explicit cancel-stop for an in-flight run (must use bgi_close) and no delete/uninstall tools for groups, one-dragon configs, or installed scripts.