No user-submitted related servers found.
Scored across 5 tools
project_query, analyze, and code_check all answer questions about code and overlap meaningfully (analyze subsumes existence-checking that code_check specializes). run_tool further muddies boundaries by bundling node_inspect, relation_trace, and change_review, which duplicate project_query and index_update concerns. Descriptions help, but an agent must reason carefully to pick the right entry point.
Names are all snake_case and readable, but the convention is mixed: project_query, index_update, and code_check use noun_verb, analyze is a bare verb, and run_tool uses verb_noun. There is no single predictable pattern, though it is far from chaotic.
Five top-level tools is a reasonable, well-scoped surface for a code-intelligence server. However, run_tool smuggles roughly twenty distinct operations (node_inspect, map_view, history_search, etc.) into a single tool, artificially compressing what is effectively a much larger toolset.
The surface covers querying, indexing, evidence-backed analysis, structure/impact/history inspection, and test tracing — solid lifecycle coverage for a read/analysis server. Gaps are minor, e.g. no direct workaround for edit application or non-listed language import checking beyond the not_checked fallback.
