memory-manager-mcp

Save memory

save_memory

Store distilled project information—decisions, requirements, and solutions—into a persistent knowledge base, so future coding sessions can retrieve important context.

Instructions

Save a curated memory for the current project. Use for decisions, requirements, architecture, tasks, problems, solutions, progress, facts, preferences, constraints and discoveries. Do NOT save raw conversation text — save distilled, useful information.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "content": "<content>"
    },
    "name": "save_memory"
  }
}

Input Schema

Name	Required	Description
`id`	No	Provide to update an existing memory.
`tags`	No
`type`	Yes	Memory type.
`source`	No	Where this came from, e.g. "user", "debugging".
`agentId`	No	Identifier of the calling agent/client, e.g. "cursor", "vscode", "claude-cli".
`content`	Yes	The distilled information to remember.
`sessionId`	No
`confidence`	No	0..1, default 0.7.
`importance`	No	0..1, default 0.5.
`workspacePath`	No	Workspace directory of the project. Defaults to the server working directory.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Aug 17, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It adds useful curation guidance but fails to disclose critical traits like whether saving is idempotent, whether it updates or creates when an id is provided, or what the side effects are. This is a significant gap for a write operation.

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 short sentences, front-loaded with the purpose and then a valuable usage/exclusion note. Every word earns its place; no filler or redundancy.

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?

With no annotations and an output schema absent, the description provides a clear scope and use cases but misses behavioral details like update semantics, interaction with other memory tools (e.g., get_memory, search_memory), and lifecycle. It is adequate but has notable gaps for a tool this complex.

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 80%, so most parameters (id, type, content, etc.) are already documented. The tool description adds minimal parameter context beyond the concept of 'curated' and 'distilled' content, which aligns with the schema but does not go further. Baseline 3 is appropriate.

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 clearly states 'Save a curated memory for the current project' with a specific verb and resource. It lists the categories it applies to (decisions, requirements, architecture, etc.) and explicitly excludes raw conversation text, distinguishing it from sibling memory tools.

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 provides explicit when-to-use guidance via the list of memory types and a clear exclusion ('Do NOT save raw conversation text'). However, it does not name alternative tools for specific scenarios (e.g., record_decision for decisions), so it falls just short of explicit alternative naming.

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

Deploy Server