Skip to main content
Glama
bedrock-map-builder-mcp

bedrock-map-builder-mcp

by xRookieFight

world_restore

Destructive

Replace a managed Minecraft: Bedrock Edition world with a backup, saving its current state first so the replacement can be undone.

Instructions

Replace a managed world with one of its backups. The current state is backed up first, so this can be undone too.

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": {
      "world": "<world>",
      "backup": "<backup>"
    },
    "name": "world_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
worldYes
backupYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The destructiveHint=true annotation already flags the overwrite; the description adds genuinely new information beyond it by disclosing that the current state is backed up first and that the operation is therefore reversible. It stops short of saying whether the pre-restore backup persists, where it lands, or what happens if the named backup is invalid.

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?

Two short sentences, the action stated first and the reversibility guarantee second. No filler, no repetition of the name, and nothing that could be cut without losing information.

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?

For a destructive two-parameter mutation with no output schema and zero parameter documentation, the description covers the core action and the undo path but leaves gaps: the identifier format for 'backup', permission requirements, and failure behavior on a missing or mismatched backup are all unstated.

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 0% for both required parameters, so the description has to compensate. It does add some meaning – 'world' is the target and 'backup' must be one of that world's own backups, implying it comes from world_backups – but it never clarifies whether 'backup' is a name, ID, or timestamp, nor any format constraints.

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 gives a specific verb and resource ('Replace a managed world with one of its backups'), which makes clear this is the inverse of the backup-creating siblings. An agent can distinguish it from world_backup and world_backups without opening any schema.

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?

Usage is only implied by the wording 'Replace ... with one of its backups' – the natural read is rollback after a bad change, but the description never says 'use this to roll back' or names a condition or alternative. No exclusions or prerequisites (e.g. that the backup must already exist) are stated.

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