memini
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recall_project_contextA | Load the most important project memories (failed attempts, fragile files, decisions, deployment rules) before starting work. Call this at the start of a task. |
| check_before_editingA | Check whether a file has recorded risks, failed attempts, or fragile-file warnings BEFORE editing it. Always call this before modifying configuration or deployment files. |
| remember_decisionA | Record an important design or implementation decision and WHY it was made, so future sessions do not relitigate or reverse it unknowingly. |
| remember_failed_attemptA | Record an approach that was tried and FAILED, so no future session repeats it. Include what was tried, why it failed, and what the actual fix was (if known). |
| remember_fragile_fileB | Mark a file as fragile/risky so future sessions get a guardrail warning (or block) before touching it. |
| end_session_summaryB | At the end of a work session, record what changed, what worked, and what failed. Creates a session summary and proposes durable memories. |
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 6 tools
Each tool has a clearly distinct purpose: checking before editing, recalling context, recording decisions, failures, fragile files, and session summary. No overlap in functionality.
All tools follow a consistent verb_noun pattern in snake_case (e.g., recall_project_context, remember_decision). The pattern is predictable and clear.
With 6 tools, the set is well-scoped for managing agent memory and sessions. Each tool covers a specific necessary action without redundancy.
The set covers core memory operations (load, record decisions/failures/fragile files, session summary, pre-edit check). Minor gaps exist, such as no explicit tool to list or forget memories, but the surface is largely adequate.