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_governB | 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
Each tool has a distinct verb (recall, write, organize, govern) that clearly separates reading, writing, maintenance, and governance. There is no overlap in responsibilities; an agent can confidently choose the right tool based on the action needed.
All tools follow a consistent memory_<verb> pattern, making the naming predictable and easy to navigate. The verb choices are clear and align with the tool's function.
With 4 tools, the server is well-scoped for a memory management domain. Each tool has a necessary place, and the count is neither too sparse nor overwhelming.
The tool set covers the full memory lifecycle: recall (read/search), write (create), organize (maintenance), and govern (update/delete, pin/unpin). There are no obvious dead ends or missing operations for a memory-focused server.