No user-submitted related servers found.
Scored across 18 tools
The tool families are mostly distinct: read_file* covers whole-file vs outline vs symbol access, search_* covers file/project/symbol scopes, and editing tools separate patch vs symbol replacement vs insertion. Minor overlap remains between search_in_project and search_symbol for locating definitions, and between patch_file and replace_symbol.
Most tools follow a clear verb_noun or verb_preposition_noun pattern, with consistent families such as read_file_outline/read_file_symbol and search_in_file/search_in_project. Small deviations like annotate, batch_rename, and search_symbol (without in_) do not seriously undermine the convention.
At 18 tools, the surface is slightly above the ideal 3-15 range, but the count is justified by the broad scope: context, annotations, reading, searching, diagnostics, complexity, patching, symbol refactoring, imports, and dead-code removal. A few tools could be consolidated, but none feels redundant enough to be a real problem.
The set covers the full read-edit-refactor workflow, including diagnostics after edits, symbol-aware operations, and dead-code detection. It lacks an explicit arbitrary file create/delete tool and import removal, but patch_file and the existing symbol tools cover most real workflows.