telemem
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | OpenAI API key for LLM and embeddings (required if not using other providers) | |
| TELEMEM_CONFIG | No | Path to TeleMem configuration YAML file | |
| TELEMEM_DEFAULT_USER_ID | No | Default user ID for memory operations when not explicitly provided |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_memoryA | Store a fact, preference, or conversation in TeleMem long-term memory. Provide |
| search_memoriesA | Semantic search over TeleMem memories. Returns the matching memories as one consolidated text passage (TeleMem fuses related memories). Shared event memories (pseudo-user "events") are searched automatically. |
| get_memoriesA | List stored memories for a user/agent/run with their memory_ids. Use user_id "events" to list shared conversation-event memories. |
| get_memoryA | Fetch a single memory by its memory_id. |
| update_memoryA | Overwrite the text of an existing memory by memory_id. |
| delete_memoryA | Delete a single memory by memory_id. |
| delete_all_memoriesA | Delete every memory in the given scope. Destructive: requires an explicit user_id, agent_id, or run_id — the default user is never assumed. |
| memory_historyA | Show the change history (ADD/UPDATE/DELETE events) of a memory. |
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
Each tool has a distinct role: add, get, search, list, update, delete, delete-all, and history. No overlaps or ambiguity; the descriptions clarify the differences between get_memory and get_memories.
Most tools follow a consistent verb_noun snake_case pattern (add_memory, get_memory, search_memories, update_memory, delete_memory). The exception is memory_history, which is noun_noun, breaking the pattern slightly.
The 8 tools cover the full memory lifecycle without bloat. The count is appropriate for a specialized memory server, neither sparse nor excessive.
The surface covers the complete CRUD spectrum (add, get, update, delete), plus listing, semantic search, delete-all for scope cleanup, and history tracking. No obvious gaps for the stated purpose of long-term memory management.