No user-submitted related servers found.
Scored across 23 tools
Most tools have a clearly distinct target: catalog browsing (search_blocks, describe_block, list_categories), graph editing (add_block, connect, set_parameters), and runtime control (deploy_graph, control_session, read_stream). The one risky pair is set_parameters vs update_block_settings and get_block_settings vs show_graph, but their descriptions explicitly contrast graph-edit vs live-session semantics. Only minor boundary friction remains.
The dominant pattern is snake_case verb_noun (list_categories, add_block, remove_block, save_graph, deploy_graph, read_stream). Deviations are minor and readable: noun-first status tools (backend_status, session_status) and a few verbless/bare-verb names (new_graph, connect, disconnect). No casing mixing.
23 tools is on the heavy side, but the domain genuinely spans four sub-areas (block catalog, graph editing, deployment/sessions, backend install management) and each tool covers a real operation. Nothing looks redundant enough to remove, though a couple of status tools could conceivably be merged.
The lifecycle is well covered end to end: discover blocks, build/edit a graph, validate, save/load, deploy, control the session, and read live data, plus backend install and attach management. Small gaps exist around exposing graph export/serialization details or bulk session cleanup, but agents can work around them with existing tools.