Scored across 15 tools
Most tools target distinct operations such as status checks, search, context assembly, knowledge lifecycle management, and code-graph analysis. The main overlap is between list_entities and query_entities, and to a lesser extent search/query_entities, but the descriptions largely clarify when each should be used.
Names are consistently snake_case and predominantly follow a verb_noun pattern (get_status, list_entities, create_entity, get_callers, etc.). A few deviations are single-verb or less patterned names like search and consolidate, but the overall convention is predictable.
At 15 tools, the set is well-scoped for a knowledge/code-graph server covering status, retrieval, lifecycle management, and graph queries. Each tool maps to a meaningful operation, including hook-driven and housekeeping tools, without excessive surface area.
The server covers core knowledge lifecycle (create, update, reject, verify, consolidate), retrieval (search, query_entities, get_context), and code-graph analysis (get_callers, get_impact, find_orphans). Minor gaps exist, such as no direct get_entity-by-id for full content and no outgoing dependency/callee query, but agents can work around them via search and existing browse tools.
