memory-bank-mcp

Overview Schema Source Related Servers Discussions Admin

restore_backup

Restore your Memory Bank to a previous state using a specified backup. Optionally, creates a backup of the current state before restoring to prevent data loss.

Instructions

Restore the Memory Bank from a specified backup. By default, creates a backup of the current state before restoring.

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": {
      "backupId": "<backupId>"
    },
    "name": "restore_backup"
  }
}

Input Schema

Name	Required	Description	Default
`backupId`	Yes	The backup ID (folder name) to restore from. Use create_backup with listOnly:true to see available backups.
`createPreRestoreBackup`	No	Whether to create a backup of the current state before restoring (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.3.0Apr 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions the default backup creation, which is a safety behavior, but does not explicitly state that restoration overwrites the current state or is destructive.

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 long, front-loads the core purpose, and contains no extraneous information. Every word is meaningful.

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?

Given the tool's simplicity (2 parameters, no output schema), the description covers the essential behavior and a key default. It could mention that restoration overwrites the current memory bank, but overall it is sufficiently complete for an agent to understand.

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?

The input schema has 100% description coverage, so the baseline is 3. The tool description adds no new parameter information beyond what is already in the schema, but it does not mislead.

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 the tool's purpose: 'Restore the Memory Bank from a specified backup.' It uses a specific verb and identifies the resource, and distinguishes itself from the sibling 'create_backup' by implying this is the restore counterpart.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use or not use this tool, nor does it mention alternatives. However, the default behavior of creating a pre-restore backup provides implicit guidance on safe usage.

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