Related Servers

While many tools have distinct purposes, there is significant overlap among monitoring/status tools (system_status, monitor_agents, audit_pipeline, phoenix_verify_integrity, phoenix_recovery_health) and among board-related tools (board_convene_session, board_get_session, board_approve_gate, agent_rights, branch_authority_status, colony_*). The descriptions are detailed but the functional boundaries are fuzzy in places, especially with the many 'colony' and 'board' tools that all involve governance sessions and rights.

The naming mix is inconsistent: snake_case for most core tools (classify_decision, evaluate_threshold), but prefixes like 'board_', 'agent_', 'branch_', 'colony_', 'context_', 'governed_', 'srt_', 'gia_' create multiple naming families. Some tools use an imperative verb (e.g., approve_gate, load_memory_pack) while others are nouns (system_status, phoenix_recovery_health). The lack of a single consistent verb_noun pattern across the surface reduces predictability.

With 53 tools, the server is clearly trying to cover a massive governance and AI oversight domain, but the scope is sprawling and many tools are niche (e.g., colony_* and board_*). The count feels heavy and likely overwhelms agents; it exceeds the typical 15-tool threshold by a wide margin, making it hard for an agent to navigate and select the right tool.

The server covers many governance aspects—classification, memory packs, boards, colony autonomy, SRT, and GIA packs—but there are gaps. For example, there is a create and list for memory packs, but no explicit 'delete' or 'archive' memory pack tool, and the governance event recording is limited to two record tools. The domain is so broad that completeness is hard to judge; core workflows (classification, gating, audit, monitoring) seem covered, but the colony and board features are missing some lifecycle actions (e.g., update a charter, dissolve a session).