No user-submitted related servers found.
Scored across 6 tools
Each tool has a clear primary role in the edit-test loop, and the descriptions distinguish dedicated tools from the general-purpose bash escape hatch. Some overlap remains because bash can also search, read, and run tests, but the guidance to use the specialized tools first keeps confusion limited.
All names use lowercase snake_case and are readable. The set is mostly consistent, though it mixes action-style names like search, run_tests, and view_file with command/noun-style names like diff and bash.
Six tools is well scoped for a sandboxed code-repair workflow: find, read, edit, test, inspect, and shell. Each tool has a clear purpose and none feels redundant or excessive.
The surface covers the full core lifecycle for bug fixing: searching code, viewing files, editing, running tests, checking diffs, and falling back to shell commands. Missing edge operations like file creation or deletion are handled through bash, so there are no dead ends.