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

bedrock-map-builder-mcp

by xRookieFight

world_backup

Creates a consistent full copy of a running Minecraft Bedrock world using save hold, query, and resume, so you can back up maps without stopping the server.

Instructions

Full copy of a managed world. While the server runs it uses save hold/query/resume, so the copy is consistent.

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

Input Schema

NameRequiredDescriptionDefault
labelNo
worldYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With annotations empty, the description carries the full burden, and it does disclose one genuinely useful behavioral fact: while the server is running it uses save hold/query/resume so the copy is consistent. That is real value beyond structured fields. However, it omits where the copy is written, whether the operation blocks or how long it takes, size/cost implications, and any permission requirements for a potentially expensive full-world copy.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core purpose and followed by the consistency mechanism. Nothing is padded, though the brevity borders on under-specification given the missing parameter and routing information.

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 destructive-adjacent, potentially long-running full-copy operation with no annotations, no output schema, and two undocumented parameters, the description is too thin. It never says what the tool returns (a backup id? path?), how the label is used, or how the resulting artifact is later restored.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, and the description compensates for neither. "world" can be loosely inferred from "a managed world," but "label" (maxLength 40) is never mentioned — the agent gets no signal that it names/tags the resulting backup or whether it is optional.

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?

"Full copy of a managed world" names both the action (full copy) and the resource (managed world), so an agent knows it produces a backup artifact rather than mutating world contents. It does not distinguish itself from nearby siblings such as world_export, world_restore, or world_backups, so differentiation is left to inference.

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?

There is no explicit when-to-use guidance, no prerequisites, and no named alternative. The reader must guess whether this differs from world_export (export vs. internal backup copy) or how it relates to world_backups/world_restore; nothing in the text routes the agent between them.

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