Skip to main content
Glama

mem_save

Destructive

Save observations, decisions, and discoveries to persistent memory that AI coding agents recall when relevant. Organize memories by type and scope for precise retrieval.

Instructions

Save an observation to persistent memory. Without session_id, uses a stable manual-save session for the detected project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOne of: bugfix, decision, policy, architecture, discovery, pattern, config, preference. The category is a search filter, so a word outside this list is a memory that filtering never returns — a real store collected `implementation`, `feature` and `manual` that way. Close synonyms are folded on the way in; anything else is kept verbatim.manual
scopeNoMemory scope: project, personal, or global. A label for filtering later — a personal memory still belongs to this project and reads narrowed to another one will not return it.project
titleYesShort searchable title.
contentNoFull observation content.
projectNoProject owning this observation. Accepted only when it matches the detected project, the process override, or a project the store knows.
tool_nameNoName of the tool that produced the observation.
topic_keyNoStable key used to revise an evolving observation instead of inserting another.
session_idNoSession identifier. Defaults to manual-save-{project}.
observationNoBackward-compatible alias for content.
capture_promptNoLink this memory to the question it answers: the prompt this process last recorded, else the session's last one, else — only when no session_id is given — the project's last from the past 30 minutes. Defaults to true. Pass false for automated saves that answer no user request.
recovery_tokenNoShort-lived token returned by an ambiguous_project error. Required with project_choice_reason.
project_choice_reasonNoMust be user_selected_after_ambiguous_project, and only after the user picked one of available_projects from an ambiguous_project error.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNoSaid when a summary was saved without a name anybody could find it by.
statusNo
projectNo
candidatesNo
judgment_idNo
observationNo
project_pathNoWhere the project lives, when the answer came from a directory.
project_sourceNo
judgment_statusNo
judgment_requiredNo
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the write nature is known. The description adds the 'stable manual-save session' default when session_id is omitted, which is valuable context. It does not elaborate on irreversibility or side effects, but the annotation covers the destructive nature. No contradictions detected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that states the primary action and a key default behavior. There is no filler or redundancy; every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high parameter count (12) and rich schema descriptions, the one-sentence description is lean. It covers the primary purpose and a key default, but it omits usage guidance and does not mention important behaviors like topic_key revision, project ambiguity handling, or capture_prompt linking. The rich schema and annotations compensate partially, but the description itself leaves contextual gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The tool description does not add anything beyond the schema's own detailed parameter descriptions (e.g., session_id default is already documented in the schema). Therefore, the description contributes no additional parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb+resource: 'Save an observation to persistent memory.' It distinguishes from sibling tools like mem_save_prompt by focusing on 'observation' rather than 'prompt', though it does not explicitly name alternatives. The core purpose is immediately understandable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use mem_save vs alternatives such as mem_save_prompt or mem_capture_passive. It mentions the session_id default behavior, which is a useful context, but it does not state explicit usage conditions, exclusions, or scenarios where another tool would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asanabrial/leteo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server