RecallVault
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Check RecallVault server health, configuration, and return a suggested context bundle for session start. |
| rememberB | Write memory (session context or permanent knowledge) to RecallVault. Creates new entry or appends to existing. |
| recallC | Search and retrieve relevant memories. Keyword match + filters + sort + window-size adaptation. |
| list_memoriesB | List memory entries with metadata overview. Useful for inventory and inspection. |
| archive_memoryA | Archive or unarchive a memory. Archived memories are excluded from recall by default. |
| update_memoryB | Update memory content or frontmatter fields. Replaces body/tags/related_files or sets reviewed/priority/archived. |
| delete_memoryA | Permanently deletes a memory file. NO RECOVERY — be sure. Use archive_memory if you may need it back. |
| set_memory_priorityA | Quickly set memory priority (1=low, 2=normal, 3=high). Higher priority memories rank higher in recall. |
| memory_setupB | Phase 3: Initialize vault with fence block and optional starter memories. Safe to call multiple times (idempotent). |
| memory_importA | Phase 4: Import existing project docs (.trae/documents/ and docs/) as semantic memories. Idempotent — skips already-imported files. |
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 10 tools
Most tools have clearly distinct purposes, but update_memory explicitly sets archived and priority fields, overlapping archive_memory and set_memory_priority. remember versus update_memory also requires care, though the descriptions distinguish create/append from replacement.
The set mixes verb_noun names like list_memories, archive_memory, and delete_memory with bare verbs like remember and recall, plus noun-first names like health_check, memory_setup, and memory_import. It remains readable, but there is no single predictable convention.
Ten tools are well-scoped for a memory vault: CRUD/search, archive, priority, setup/import, and health check. Each tool has a plausible place in the lifecycle, with no obvious bloat.
The surface covers create/append, search/retrieve, list, update, delete, archive, priority, setup/import, and health. There is no dedicated get-by-id or bulk operation, but recall and list_memories cover retrieval and inspection well enough for core workflows.