Skip to main content
Glama
Sign In
MCP SmallEdit

MCP SmallEdit

by MikeyBeez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

restore_backup

Restore files from their most recent backup copies to recover previous versions or fix errors, with options to preserve backup files after restoration.

Instructions

Restore a file from its most recent backup (.bak)

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

Input Schema

NameRequiredDescriptionDefault
fileYesFile to restore from backup
keepBackupNoKeep the backup file after restoring

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but lacks behavioral details. It doesn't disclose if this is destructive (overwrites the original file), requires specific permissions, has side effects, or what happens on failure (e.g., if no backup exists).

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It misses critical details like behavioral risks (e.g., data loss), error handling, and output expectations, leaving gaps for safe agent invocation.

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 parameters are documented in the schema. The description adds no additional meaning beyond implying '.bak' extension context, but doesn't clarify parameter interactions (e.g., how 'keepBackup' affects the restore process).

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 clearly states the action ('Restore') and resource ('a file from its most recent backup'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_backups' beyond the basic verb, missing explicit contrast.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., requiring a backup to exist), exclusions, or comparisons to siblings like 'list_backups' for checking available backups first.

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