leafmem
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 |
|---|---|
| memory_recallB | Recall long-term memory: build prompt-ready recall context, search/get/list records, build a task window, or read active context/experience. |
| memory_writeC | Write memory: remember a durable record, commit a host-distilled session (returns maintenanceRequest when deeper governance is due), append a task entry, or distill active context/experience. |
| memory_organizeC | Curate memory: prepare/apply host-mediated active maintenance, distill principles (reflect), refresh the user profile (profile), decay stale records (decay), or maintain active experience (calibrate/rebuild). |
| memory_governC | Manage memory: update or delete records (explicit scope required), attribute recall usefulness, or pin/unpin a record against decay. |
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
The four tools have distinct high-level purposes (recall, write, organize, govern), but their descriptions bundle many sub-operations with overlapping concepts. Notably, 'distill active context/experience' in memory_write overlaps with 'distill principles' and 'maintain active experience' in memory_organize, which could confuse an agent about which tool to use for those tasks.
All tool names follow a consistent memory_verb pattern in snake_case, with clear, distinct verbs (recall, write, organize, govern). This predictability makes the set easy to navigate.
Four tools is a reasonable count for a memory management server, grouping operations into lifecycle phases. However, each tool is very broad and handles many sub-operations, which could argue for slightly more granularity.
The tool surface covers the full memory lifecycle: reading/searching (recall), creating/updating (write), curation/maintenance (organize), and governance (update/delete/attribute). No obvious gaps for the stated domain.