Remember-Memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| remember_memoryC | Stores a memory with optional tags in a specified category |
| retrieve_memoriesC | Retrieves all memories from a specified category |
| remove_memory_categoryC | Removes all memories within a specified category |
| remove_specific_memoryC | Removes a specific memory within a specified category |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: remember_memory stores, remove_memory_category deletes a whole category, remove_specific_memory deletes a single memory, and retrieve_memories fetches. No overlap exists, making selection unambiguous.
All tools follow a consistent verb_noun pattern with snake_case, using clear verbs like remember, remove, and retrieve. The naming is predictable and uniform throughout the set.
With 4 tools, this server is well-scoped for memory management, covering core operations (store, retrieve, delete specific, delete category) without bloat or missing essentials. Each tool earns its place.
The tool surface provides complete CRUD-like coverage for the memory domain: create (remember_memory), read (retrieve_memories), delete (remove_specific_memory and remove_memory_category). No obvious gaps exist for basic memory operations.