memento-context
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 |
|---|---|
| init_mementoB | MANDATORY: Call this ALWAYS as the FIRST action of EVERY session, NO EXCEPTIONS, before anything else, even for greetings or simple questions. Already loads all mementos, calling get_mementos right after is redundant. |
| get_mementosB | Returns active mementos. Use scope=all for both global and repository memory, or scope=global/repo to inspect just one area. |
| save_mementoA | Saves a persistent memento across sessions. The AI must choose whether it belongs to global memory or the current repository. Requires init_memento or get_mementos first. |
| save_conversationA | Saves a conversation or summary as a memento with attachments. Only use this on explicit user request. Requires init_memento or get_mementos first. |
| save_memento_attachmentsA | Copies files from the filesystem into the attachments directory of an existing memento. Only use this on explicit user request. Requires init_memento or get_mementos first. |
| get_memento_attachmentsA | Reads and returns all attachment files for a specific memento. Use this only when the extra detail is needed. Requires init_memento or get_mementos first. |
| delete_mementoA | Deletes an existing memento by its exact ID, regardless of whether it is global or repository-scoped. Requires init_memento or get_mementos first. |
| move_mementoA | Moves an existing memento from global to repository scope or from repository to global scope. Use when the user asks to reclassify stored memory. Requires init_memento or get_mementos first. |
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 8 tools
Tools are largely distinct: init/get/save/delete/move cover clear lifecycle operations, and attachment/conversation save are separately named. Some overlap exists between save_memento and save_conversation (both persist mementos, differing mainly by whether attachments are included), but descriptions help disambiguate. The confusing 'mandatory init first' pattern creates redundancy concern but not ambiguity.
Most tools follow a consistent verb_memento pattern: init_memento, get_mementos, save_memento, delete_memento, move_memento, get_memento_attachments, save_memento_attachments, save_conversation. Minor deviation with save_conversation breaking the pattern, and pluralization of get_mementos vs singular memento naming is slightly inconsistent.
8 tools is well within the ideal 3-15 range for a memory/context management server. Each tool serves a clear purpose in the lifecycle: initialization, retrieval, saving, attachment handling, deletion, and movement. No unnecessary tools present.
The tool surface covers the full memento lifecycle: init, read (with scope filtering), create, attach files, delete, move, and conversation capture. Minor gaps exist—there's no update/edit operation for an existing memento's content (only delete then save), and no search/filter tool beyond basic scope filtering.