The tool set is extremely large with many overlapping names. For example, there are multiple 'confirm' tools (semantic_confirm, business_mapping_confirm, knowledge_confirm, confirm) and many 'validate' tools (code_facts_validate, edge_validate, node_semantic_validate, business_candidates_validate, business_mappings_validate). Generic verbs like 'update', 'query', 'publish', and 'job' further blur boundaries, making it nearly impossible for an agent to reliably select the correct tool without detailed descriptions.

Most tool names use snake_case, but the pattern is inconsistent. Some follow verb_noun (e.g., list_scopes, list_domains, search_nodes), but many invert to noun_verb (e.g., graph_context_get, node_batch_get) or use awkward structures like 'business_directory_batch_upsert'. Additionally, several tools are single words without a pattern (e.g., ingest, update, push, query, status, health), which breaks consistency.

With 77 tools, the server is excessively large for a typical MCP context. The stated domain of code-context-storage is not so broad as to justify this number, especially when many tools appear to be variations of the same operation (e.g., multiple upsert, validate, and confirm tools). This creates a maintenance and selection burden without clear benefit.

Despite the massive number of tools, there are notable gaps. For instance, there are upsert operations for nodes, edges, and business mappings but no corresponding delete or remove operations. Similarly, there are get and search operations but no clear lifecycle management for jobs beyond cancel/resume. The bloat suggests coverage is scattered rather than systematically complete.