No user-submitted related servers found.
Scored across 30 tools
Multiple tools have overlapping purposes: memory_init, memory_bootstrap, memory_onboard, and memory_agent_join all serve onboarding or initialization roles. Similarly, memory_search, memory_search_vector, and memory_search_archive are three search variants, and memory_status, memory_token_usage, and memory_doctor all provide health/status information. While descriptions clarify some differences, the boundaries between these tools are not immediately obvious, creating selection ambiguity.
All tool names follow a strict `memory_` prefix followed by a verb_noun pattern, using snake_case throughout (e.g., memory_create_ticket, memory_read, memory_search_archive). This is highly consistent and predictable, making it easy to infer the action and target of each tool.
At 30 tools, the server feels over-scoped. Many tools are highly specialized and could be merged or parameterized, such as the three search tools or the multiple onboarding variants (memory_init, memory_bootstrap, memory_onboard). The count exceeds the threshold for 'too many' (25+), which burdens agents with a large surface to navigate.
The tool set covers core memory and ticket workflows thoroughly: memory lifecycle (write, read, search, compact, archive, checkpoint), ticket lifecycle (create, claim, submit, review, cancel, terminate, list), and collaboration features (handoff, briefing, agent_join). Minor gaps exist, such as no explicit memory deletion (only unpin) and no direct ticket editing, but these are workable with existing tools.