local-memo
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memo_getA | Retrieve a previously saved conversation context by its ID. |
| memo_setA | Save the current conversation context for handoff to another session or agent. Returns a short ID for retrieval. |
| memo_listA | List all saved memos that haven't expired yet. |
| memo_deleteA | Delete a saved memo by its ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| memo set | Save the current conversation context for later restoration |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct operation on memos: get retrieves, list enumerates, set saves, delete removes. There is no overlap or ambiguity between them.
All tools follow the consistent pattern memo_<verb> (get, list, set, delete). The naming is uniform and predictable.
Four tools is a well-scoped count for a simple memo/context storage service. Each tool is necessary and none are redundant.
The tool surface covers the full lifecycle of memos: create (set), read (get), list, and delete. No obvious missing operations for the stated purpose.