memex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_MAX_POOL_SIZE | No | Override max pool size for asyncpg (default 20) | 20 |
| SUMMARIZATION_ENABLED | No | Toggle the background summarization job | true |
| SUMMARIZATION_THRESHOLD | No | Episodic count to trigger per pair | 100 |
| SUMMARIZATION_BATCH_SIZE | No | Oldest N memories to condense per run | 50 |
| SUMMARIZATION_INTERVAL_SECONDS | No | How often the job wakes up | 300 |
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 |
|---|---|
| store_memoryA | |
| search_memoriesA | |
| delete_memoryA | |
| count_memoriesB | |
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 4 tools
Each tool has a clearly distinct purpose: storing, searching, counting, and deleting memories. No two tools overlap in functionality, so an agent can easily select the correct one.
All tool names follow a verb_noun pattern in snake_case (store_memory, search_memories, count_memories, delete_memory). The slight plural/singular variation is negligible and does not break consistency.
Four tools is an appropriate number for a focused memory server. Each tool serves a core operation without unnecessary bloat or missing essentials.
The set covers create, read (search and count), and delete operations for memories. An update tool is missing, but that is often handled by delete+store. The lack of a direct get-by-ID tool is a minor gap.