No user-submitted related servers found.
Scored across 5 tools
Each tool has a clearly distinct access pattern: single-by-ID retrieval (get_voice_memory), keyword search (search_voice_memories), recency listing (get_recent_memories), tag enumeration (list_voice_tags), and write (save_voice_memory). An agent can easily choose between search vs. recent vs. get-by-UUID based on descriptions.
All tools follow a verb_noun pattern (get_, search_, list_, save_), which is consistent. Minor deviation: the noun form shifts between 'voice_memory', 'voice_memories', 'recent_memories', and 'voice_tags', which is readable but not perfectly uniform.
Five tools is well-scoped for a voice-memory store: one write, three read/query paths, and one tag-listing helper. Each tool earns its place without redundancy.
The read/create and search surface is solid, but there is no update or delete operation for memories, and no way to manage tags directly. For a memory store these are notable gaps that could cause dead ends if an agent needs to correct or remove a record.