No user-submitted related servers found.
Scored across 9 tools
Each tool has a sharply distinct role: search by description, read by known name, read a module wiki page, direct callers vs callees, transitive impact, repository listing, session memory recall, and feedback marking. The descriptions explicitly cross-reference the neighbours (find_callers vs impact_of vs find_callees; search_code vs get_symbol) and state when to prefer each, eliminating overlap.
Most tools follow a verb_noun pattern (search_code, get_symbol, find_callers, read_wiki, list_repositories, mark_used). A few deviate: impact_of is noun/prepositional and recall is a bare verb, which is slightly inconsistent but still readable and unambiguous.
Nine tools sit comfortably in the well-scoped 3-15 range. Each maps to a distinct step in a code-investigation workflow (discover repo, search, read, navigate calls, gauge impact, consult/write memory), none feels redundant.
Covers the core lifecycle well: repository discovery, search, symbol/source reading, wiki pages, forward and backward call navigation, transitive impact, plus memory recall and feedback. Minor gaps exist—no way to enumerate symbols within a file or module, and no explicit tool to write/record a new fact (facts are distilled automatically), but agents can work around these.