No user-submitted related servers found.
Scored across 39 tools
Many tools occupy overlapping investigative territory: scout, similar, query, find_implementations, trace, and change_kit all help locate or understand code, while investigate and orchestrate both run fused workflows. The descriptions are detailed, but an agent would struggle to reliably pick between these parallel search/investigation paths and related post-edit tools like since, review, edit_cycle, and verify.
Names are consistently snake_case, which is good, but the style mixes bare verbs (investigate, plan, query, review, trace, verify), bare nouns (hotspots, browser, docs, glossary, hints), and prefixed groups (agent_*, orchestration_*). The pattern is readable but not predictable enough to infer what a tool does from its name alone.
At 39 tools, this is well into the 'too many' range even for a broad code-assistant server. Several tools are redundant or could be consolidated, such as the orchestration cluster (orchestrate, orchestration, orchestration_feedback, orchestration_memory, run_trace) and the overlapping edit/review cluster (edit_cycle, since, review, verify, apply_patch_workspace_file).
The surface is broad, but descriptions repeatedly reference tools that are not exposed: context, impact, test_impact, context_bundle, diagnostics, review_diff, kickoff, docs_add, and orient. The set also lacks an explicit create-file workflow, only patching existing files. These missing pieces create dead ends and force agents to work around gaps in the advertised workflow.