Skip to main content
Glama

save_memory

Record decisions, bug fixes, discoveries, and user preferences for future sessions. Use stable topic keys to update existing memories and keep a local markdown backup.

Instructions

Save a memory for future sessions. MUST be called after: (1) architecture decisions — record what was chosen, why, and what was rejected, (2) bug fixes with root cause — record symptom, root cause, fix, and prevention, (3) important discoveries — record finding and its implications, (4) user preferences — record preference and reasoning. Use topic_key for cross-session dedup (same project+topic_key updates existing memory). By default also writes a local markdown backup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoOptional host identifier, e.g. codex-cli, claude-code, api, cli.
textYesMemory text content
filesNoList of related file paths
scopeNoMemory scope: 'project' (default, only this project) or 'global' (visible in all projects). Use 'global' only for explicitly cross-project preferences or knowledge.
titleNoOptional title
branchNoGit branch label. If omitted, the server auto-detects from the MCP process current working directory. Pass an explicit value to override (e.g. when the calling agent is not running inside the project's git checkout).
projectNoProject name
topic_keyNoStable topic identifier for cross-session dedup. Same project+topic_key updates existing memory instead of creating new one. Format: kebab-case descriptive key, e.g. 'fts5-search-strategy', 'auth-middleware-design'.
local_pathNoOptional local markdown path for backup copy. Relative paths are resolved from current working directory. The resolved path must fall within the remem data directory (REMEM_DATA_DIR); paths outside that boundary are rejected.
session_idNoOptional host session id. When provided, Stop summary promotion can suppress exact duplicate candidates from the same session.
memory_typeNoMemory type: decision, discovery, bugfix, architecture, preference. Defaults to 'discovery'.
claim_sourceNoOptional claim source label. Defaults to manual_save for MCP calls.
claim_enabledNoOverride the session claim toggle. Defaults to true; set false to preserve legacy save behavior without claim rows.
created_at_epochNoOptional override for the memory's creation timestamp (Unix epoch seconds). Use only for backfilling historical entries; defaults to now when omitted.
local_copy_enabledNoOverride the local markdown backup toggle. Default behavior (when omitted) is controlled by the server config.
acknowledge_patternNoExplicitly acknowledge an instruction-pattern match in direct save text after human review. Must match the detected pattern id, e.g. override_previous_instructions.
reference_time_epochNoExplicit episode/source event time (Unix epoch seconds) used to resolve relative dates. Preferred for historical backfills; created_at_epoch is used only when this is omitted.
Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It discloses non-obvious behaviors: 'same project+topic_key updates existing memory' (dedup/update) and 'By default also writes a local markdown backup' (side effect). This goes beyond the obvious 'save' semantics.

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 two sentences plus a scannable list. The main purpose is front-loaded, and every sentence earns its place by conveying trigger conditions, dedup behavior, or default backup behavior. No wasted words.

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

Completeness4/5

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

For a tool with 17 parameters, the description covers the core usage contexts, dedup, and backup, which are the most decision-relevant aspects. It does not explain return values (no output schema) or every parameter, but the schema provides rich per-parameter descriptions, so the description is complete enough for selection and correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds meaning for topic_key by explaining cross-session dedup and update behavior, and for local backup by noting the default side effect. This adds value beyond the schema's per-parameter descriptions.

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

Purpose5/5

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

The description opens with a specific verb+resource ('Save a memory for future sessions') and further clarifies scope by listing concrete trigger scenarios. This distinguishes it from sibling retrieval/search tools, which have different purposes.

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

Usage Guidelines4/5

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

The description explicitly states when this tool MUST be called (architecture decisions, bug fixes, discoveries, user preferences), providing clear context for use. It does not explicitly name alternatives or when-not-to-use scenarios, but the trigger list is strong and actionable.

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/majiayu000/remem'

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