No user-submitted related servers found.
Scored across 34 tools
Each tool targets a distinct operation across memory, messaging, governance, and identity, and the descriptions clearly separate near neighbors like sage_inbox, sage_messages_receive, and sage_message_history. A few pairs (sage_remember vs sage_reflect vs sage_turn, sage_message_replies vs sage_message_status) could be confused at a glance, but the detailed descriptions resolve most ambiguity.
All 34 tools share the sage_ prefix and snake_case, and most follow a verb_noun pattern like sage_remember, sage_recall, and sage_message_send. Deviations include several noun-style commands (sage_backlog, sage_inbox, sage_directory) and a singular/plural mismatch between sage_message_* and sage_messages_receive.
At 34 tools, the surface is above the comfortable range and spans four distinct subsystems: memory, messaging, identity/governance, and task tracking. Each tool is individually justified, but the sheer number makes discovery and tool selection heavier than ideal for an agent.
The surface covers the core lifecycle well: memory create/read/list/link/deprecate, task create/update/backlog, full messaging send/receive/reply/history, and registration/governance operations. Minor gaps exist, such as no explicit non-replacement memory update and no deregistration tool, but agents can work around these.
