No user-submitted related servers found.
Scored across 6 tools
Most tools have distinct purposes: analyze_change_impact focuses on modification consequences, analyze_dependencies finds what depends on a module, get_function_call_graph shows function call relationships, and the last three handle repository management. However, analyze_dependencies and get_function_call_graph could be confused as both involve dependency/call analysis, though their descriptions clarify one is module-level and the other function-level.
The naming follows a consistent verb_noun pattern throughout (e.g., analyze_change_impact, get_function_call_graph, list_repositories), with all tools using snake_case. The only minor deviation is that 'initialize_graph' uses a verb without a clear noun object, but it still fits the overall pattern.
With 6 tools, the count is well-scoped for a code analysis server. It covers core functions like impact analysis, dependency tracking, call graph generation, and repository management, with each tool earning its place without being overwhelming or too sparse.
The server covers key code analysis operations (impact, dependencies, call graphs) and repository management, but there are notable gaps. For example, it lacks tools for updating or deleting initialized repositories, and there's no way to clear or reset graphs, which could leave agents in dead ends when managing repository states.