Scored across 39 tools
The search tools heavily overlap: search_code, search_bodies, search_content, semantic_search, smart_search, and lookup_symbol all find code but with subtly different scopes, requiring the agent to internalize lengthy 'when to use' rules. The reindex pair reindex_file and reindex_file_impl are nearly identical in name and description. Some tools are distinct (get_vector_table, find_dead_code), but the search family creates real selection risk.
Naming is a mix of get_*, find_*, search_*, lookup_, list_, reset_, reindex_, check_, and configure_ verbs. Within groups it is consistent (find_callers, find_callees_recursive, find_references), but find_all_callers_recursive vs find_callers_recursive vs find_callers and reindex_file vs reindex_file_impl break the pattern. The recurring shared args and project/variant/image suffixes are consistent, but verb style is not unified.
39 tools is on the heavy side for a code-intelligence server. The core domain — search, call graph, symbols, files, build/index management — is broad but the count is inflated by near-duplicate tools (reindex_file/reindex_file_impl, search_code/search_content overlapping bodies, six search tools). A well-scoped set would sit closer to 20-25 tools.
The surface covers the firmware-analysis domain very well: symbol lookup, text search, call graphs, references, data flow, inheritance, dead code, vector tables, file reading, index health, project discovery, and LLM config. Missing operations are minor — there is no tool to list all symbols in a namespace or to get diffs between build variants (only per-build querying), and no explicit index-trigger tool beyond reindex_file, but these are workaround-level gaps.