memory_plus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| svm_storeB | Store a memory block in SVM (Structured Visual Memory) |
| svm_recallB | Recall memory blocks from SVM by keywords |
| svm_forgetB | Delete a memory block by key |
| svm_listC | List all memory blocks |
| svm_statsC | Get SVM memory statistics |
| svm_auditC | Query SVM audit log |
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 6 tools
Each tool has a clearly distinct operation on memory: audit (log query), forget (delete), list (list all), recall (keyword search), stats (statistics), store (create). No overlap in purpose.
All tools follow the pattern 'svm_<verb>', using consistent snake_case and lowercase verbs. The naming is uniform and predictable.
Six tools cover the essential memory operations (CRUD plus audit and stats) without being excessive or too sparse. The scope is well-balanced for a memory management server.
Core operations create (store), read (recall, list), and delete (forget) are present. Audit and stats provide additional oversight. An explicit update operation is missing, but store may serve as upsert, so gap is minor.