Skip to main content
Glama
Sign In
memory-bank-mcp

memory-bank-mcp

by diaz3618
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

create_backup

Create timestamped backups of your Memory Bank state to safeguard project context, decisions, and progress. Choose to list existing backups or specify a custom backup directory.

Instructions

Create a backup of the current Memory Bank state, or list existing backups. Backups are stored in the parent directory with timestamped names.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
backupDirNoOptional custom directory to store the backup. If not provided, uses the parent of the memory bank directory.
listOnlyNoIf true, lists existing backups instead of creating a new one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Discloses backup storage location and naming pattern (parent directory, timestamped) but does not mention potential side effects like disk usage or performance impact, which is acceptable for a straightforward tool.

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?

A single sentence that is clear and compact, with 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?

Adequately covers the two modes and storage details, but lacks information about return values or confirmation messages, which would be helpful for an agent.

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 covers both parameters with descriptions, and the description adds context by explaining backupDir defaults to parent directory and how listOnly switches behavior, going beyond schema.

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 creates or lists backups of the Memory Bank state, which is specific and distinguishes it from siblings like restore_backup.

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 implies two modes (create vs list) but lacks explicit guidance on when to use each or how this tool relates to restore_backup, leaving some ambiguity.

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

Deploy Server

Other Tools