Skip to main content
Glama

Restore a world backup

restore_world
Destructive

Replace the current Minecraft world with a selected backup while preserving the existing world in a timestamped backup folder; stop the server first.

Instructions

Replaces the world with a backup from backup_world. The server must be stopped. The current world is not deleted: it is moved into the backup folder as replaced-. status lists the backups.

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

Input Schema

NameRequiredDescriptionDefault
nameYesBackup name from status, for example world-2026-01-31T12-00-00-000
confirmNoSet true only after the person agreed to this change (needed while confirmDestructive is on).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true; the description goes further by disclosing recoverability semantics that an agent cannot infer elsewhere: the current world is not deleted but moved to the backup folder as replaced-<time>. It also states the preconditions under which the operation will succeed.

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?

Three short sentences, front-loaded with the action, then the precondition, then the safety detail, then the pointer to the name source. No filler or repetition.

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 destructive two-parameter tool with a fully documented schema, the description covers what it does, the operational prerequisite, and the recovery path. It does not say what happens if the server is running or that confirmation may be required, but the schema and annotations carry those details.

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 coverage is 100%, and the schema already says the name comes from status with an example format, so the description mostly restates that. The confirm parameter, the one with genuine behavioral weight, is not mentioned in the description at all; baseline 3 applies.

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?

States a specific verb and resource ("Replaces the world with a backup") and ties the operation to the sibling that produces the input (backup_world), so it is distinguishable from backup_world, status, and other world-modifying tools at a glance.

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?

Gives a hard precondition ("The server must be stopped") and routes the agent to status for obtaining valid backup names. It stops short of an explicit when-not statement or naming alternatives such as undo, but the required-state condition is clear guidance.

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