No user-submitted related servers found.
Scored across 23 tools
Most tools target clearly distinct resources or actions, and descriptions draw explicit boundaries between similar areas such as search_nodes vs get_node and lineage vs impact_analysis. The main mild overlap is in the exploration cluster (get_node, list_edges, lineage, impact_analysis), where an agent may need to read descriptions carefully to choose the right scope.
The set predominantly follows a readable snake_case verb_noun pattern such as list_sources, create_graph, search_nodes, and delete_semantic_context. A few noun-only exceptions like lineage, impact_analysis, server_info, graph_health, and ossie_guide are still clear but slightly break the pattern.
At 23 tools the surface is on the heavy side, but the domain is broad: graph/source management, node exploration, semantic-context CRUD, Ossie import/export/validation, agent testing, and preference checking. Each tool maps to a recognizable workflow rather than obvious filler, so the count is high but defensible.
Coverage is strong across the core lifecycle: server/graph discovery, graph creation and update, source listing/addition/removal, node search and inspection, lineage/impact, semantic-context search/create/update/delete, and Ossie workflows. The main minor gap is the absence of an explicit delete_graph operation, though the rest of the domain is well covered.