Recall
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RECALL_DB | No | Onde fica o banco. Um por projeto funciona bem. Também pode ser passado como --db. | ~/.recall/memory.db |
| RECALL_EMBEDDINGS | No | hash (local e instantâneo), minilm (semântico, precisa do pacote opcional @huggingface/transformers e baixa o modelo uma vez) ou none (só BM25). | hash |
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 |
|---|---|
| rememberA | Store one durable fact so it is available in future sessions: decisions and their reasons, user preferences, project facts, commands, gotchas, fixes. Write it self-contained, as if read months later without this chat. Near-duplicates are merged and reinforced instead of stored twice. |
| recallA | Search long-term memory. Call it before answering questions about this user or project and when starting a task. Hybrid ranking: BM25 keywords plus local embeddings, weighted by retention (memories that are used stay strong, unused ones fade). Returned memories are reinforced. |
| forgetA | Permanently delete a memory that is wrong or must not be kept. If the fact was replaced by a newer one, prefer remembering the new fact and linking it with relation supersedes. |
| linkA | Connect two memories with a named relation so recalling one brings context from the other. |
| timelineA | Chronological log of what was remembered, recalled, reinforced, linked or forgotten, newest first. Answers questions like 'what did we decide last week?' or 'what did you look up this session?'. |
| reinforceA | Mark a memory as confirmed or useful right now so it decays more slowly. |
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 maps to a distinct memory operation: store (remember), retrieve (recall), delete (forget), connect (link), log (timeline), and reinforce. No two tools overlap in purpose, and descriptions clearly delineate boundaries.
Five of six tools are single-word imperative verbs (remember, recall, forget, link, reinforce), but timeline is a noun, breaking the verb pattern. Still readable and mostly consistent, with only this minor deviation.
Six tools are well-scoped for a long-term memory server, covering core actions without bloat. Each tool earns its place and the set feels neither thin nor heavy.
Core lifecycle is covered: create, read, delete, link, reinforce, and event log. No direct update operation, but replacing a fact via remember + supersedes link handles it; minor gap but workable.