No user-submitted related servers found.
Scored across 2 tools
The two tools have mutually exclusive purposes: memory is read-only retrieval with many actions, while memory_write is exclusively for writes (import, capture, index, tier changes). There is no overlap in functionality, so an agent can unambiguously choose based on whether it needs to read or write.
Both tool names share the 'memory' prefix, with '_write' clearly marking the write operation. This is a simple, predictable convention that mirrors the underlying domain, and there are no mixed naming styles or vague verbs.
With only two tools, the surface feels thin at first glance, but the memory tool consolidates a large set of read actions (search, latest, sessions, thread, verify, get, neighbors, index_status, probe_status) into one interface. This is a borderline case — the count is low, but the scope is narrow enough that a read/write pair is reasonable.
The tool set covers the full memory lifecycle: comprehensive reads (search, get, thread, verify, sessions, neighbors, freshness), writes (import, capture, index, demote/promote), and administrative operations (index_status, probe_status). The deliberate absence of deletion is clearly documented and does not create a dead end, as content is designed to persist.