Distill
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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_memoryA | Search team knowledge before proposing architecture, creating files, refactoring, or answering "how should we..." questions. Also search when the user says: "we decided", "last time", "previously", "remember when", "what's our pattern for". Returns compact index (~30 tokens/result). Use get_memories to fetch full content for relevant IDs only (not all results). Optionally filter by repo name, agent_id, and/or date range (after/before as ISO 8601 strings, e.g. "2025-01-01"). |
| get_memoriesA | Fetch full memory details by IDs. Batch multiple IDs in one call. Use after search_memory to get content for relevant results only. |
| get_memoryB | Retrieve a specific memory by its ID. |
| update_memoryA | Re-distill new content and supersede an existing memory. The old memory is soft-deleted. A new memory is created with the distilled version of the provided content. |
| list_recentA | List recent memories as compact index. Use get_memories for full content. Optionally filter by repo, tag, type, or agent_id. |
| forgetA | Soft-delete a memory. It will no longer appear in search results. If agent_id is provided, the memory is only deleted when it belongs to that agent. Returns 'forbidden' if the memory belongs to a different agent. |
| list_staleA | List memories that are likely stale based on age and access patterns. Stale memories have low Weibull survival scores and few accesses. Review the list and use forget() to clean up outdated knowledge. |
| get_lineageA | Trace the supersedes chain for a memory in both directions. Returns the full history: predecessors (what this memory replaced) and successors (what replaced this memory), ordered oldest to newest. Useful for understanding how a decision evolved over time. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| seed | Populate distill knowledge base from git history |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct aspect of memory management: search, retrieval by ID or batch, listing recent or stale, forgetting, updating with lineage, and tracing lineage. There is no ambiguity between tools.
Tool names follow a consistent verb_noun pattern in snake_case (search_memory, get_memories, list_recent, update_memory, etc.), with 'list_' and 'get_' prefixes clearly indicating the action.
Eight tools cover the core memory operations without being excessive or insufficient. Each tool serves a clear purpose in the memory lifecycle.
The surface covers most operations (search, retrieve, list, forget, update, lineage). The only noticeable gap is the lack of a dedicated create_memory tool, though update_memory might double as creation in some contexts.