AgentRecall
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| session_startA | [ENTRY — call FIRST, before acting] Use when the user asks to start, load, continue, resume, or open memory for a project. Set mode='lite' for a ≤500-token briefing (good for fresh conversations where the agent will pull memory on demand via recall()). |
| session_endA | [ON SAVE/EXIT — YOU must call this; nothing auto-saves] Use when the user asks to save, checkpoint, summarize, end, retain, or persist the current session. Optionally pass close_phase / open_phase to update the project pipeline narrative spine in the same call. |
| rememberA | [MID-SESSION WRITE — single fact/decision; saying it is not saving it] Use when the user asks to remember, store, note, or save a specific decision, fact, or insight. |
| recallA | [RETRIEVE — use freely, any time] Use when the user asks to recall, search, find, or look up previous memory, context, or decisions. |
| checkA | [MID-SESSION — safe any time; for alignment, before risky decisions] Use when the user asks to validate understanding, verify alignment, or check if their interpretation matches the human's intent. Also call BEFORE a high-risk action — publish, deploy, delete, credential exposure, external send/message, or any other irreversible write — passing |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| show_projects | Show the AgentRecall project status board. |
| start_project | Start or resume AgentRecall memory for a project. |
| save_session | Save the current session to AgentRecall. |
| arstart | Load full project context for a new session. Call this at the beginning of every session to recall past decisions, corrections, insights, and cross-project lessons. |
| arsave | Save everything from this session — journal, palace consolidation, awareness insights. Call at the end of every productive session. |
| arsaveall | Scan all of today's sessions across all projects and save them in one consolidated pass. Use when multiple agents ran in parallel. |
| recall-context | Quickly recall everything AgentRecall knows about a topic — searches journals, palace rooms, and cross-project insights. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Awareness | The compounding awareness document — 200-line cap, cross-project insights, trajectory, blind spots |
| Awareness State | Structured awareness state — insights array, trajectory, blind spots, compound insights |
TDQS
Scored across 5 tools
Tools map to distinct memory lifecycle phases, and descriptions provide explicit trigger conditions. However, `check` overlaps with both `recall` (retrieval) and `remember` (recording), which could cause occasional misselection despite detailed guidance.
Names are all lowercase snake_case, but the pattern is mixed: `check`, `recall`, and `remember` are bare verbs, while `session_start` and `session_end` use a noun_verb structure. Still readable, but not a uniform convention.
5 tools is well-scoped for a memory system, covering entry, retrieval, validation, recording, and exit without redundancy or bloat.
The lifecycle covers start, recall, remember, check, and end, but lacks an explicit delete/forget operation or a way to update existing memories (beyond corrections via `check`). Minor gap agents can work around.