No user-submitted related servers found.
Scored across 5 tools
Each tool maps to a distinct memory operation: search (query-based recall), get (id-based fetch), write, feedback, and link. The search-vs-get boundary is clear because one takes a query and the other takes an id, and their descriptions reinforce the distinction. No two tools appear to do the same thing.
All tools follow a strict `memory_<verb>` snake_case pattern: memory_search, memory_write, memory_feedback, memory_get, memory_link. The shared prefix plus a distinct action noun makes the whole set predictable and readable at a glance.
Five tools is well-scoped for a memory store: write, read by id, search, link, and feedback cover the intended loop without padding. No tool feels redundant or out of place, and nothing suggests a missing primitive that would require an extra tool.
The surface covers create, read, search, associate, and outcome-based lifecycle (obsolete archives), which is strong for the domain. Gaps are minor: there is no explicit delete/forget or edit tool, so removal relies on `memory_feedback(outcome='obsolete')`, and conflict resolution via keys is implied rather than directly operable.