No user-submitted related servers found.
Scored across 15 tools
Several tools overlap in purpose: get_affected_tests, get_affected_tests_by_branch, and get_rename_aware_diff all return affected test files, differing only in how they compute changed files. get_dependency_graph and get_symbol_dependency_graph also overlap at different granularities. The descriptions clarify the distinctions, but the close purposes could cause misselection.
All tools use lowercase snake_case with a verb-noun pattern, such as refresh_project, get_affected_tests, explain_impact, identify_unreachable_modules, and generate_test_command. The verbs vary by action but the convention is consistent and predictable.
15 tools is at the upper boundary of the well-scoped range and covers many facets of AST impact mapping. The count feels slightly heavier due to three variants of affected-tests tools, but overall each tool has a distinct role and the breadth is justified.
The tool set provides comprehensive coverage for impact analysis: affected tests (multiple methods), import chains, dependency graphs, coverage gaps, dead code, architecture cycles, type-only changes, API breaking changes, skeleton views, and test command generation. No critical gaps are evident for the stated domain.