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

bedrock-map-builder-mcp

by xRookieFight

world_export

Destructive

Export a managed Minecraft Bedrock world to its source, a .mcworld file, or a world folder; overwritten data is backed up and bridge pack references are removed for a clean client world.

Instructions

Write a managed world out: to='source' copies it back over where it was imported from, a path ending in .mcworld makes a file, any other path makes a world folder. Whatever gets overwritten is backed up first, and the bridge pack reference is removed so the client sees a clean world.

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

Input Schema

NameRequiredDescriptionDefault
toYes
worldYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond destructiveHint=true, it discloses two non-obvious behaviors: overwritten targets are backed up first, and the bridge pack reference is stripped so the client sees a clean world. It does not cover required permissions, failure modes, or what is returned on success.

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?

One dense sentence that front-loads the action and then enumerates modes in the order an agent needs them, with no filler. It is slightly run-on and would read better split into action plus path-mode rules.

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?

With only two required parameters, no output schema, and destructiveHint already supplied, the description covers the essential risk and outcome behavior. Remaining gaps are the meaning of 'world' and confirmation/return behavior, which are modest for a tool this simple.

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%, so the description must carry parameter meaning; it does a good job on 'to' with concrete value semantics and path-suffix rules. The 'world' parameter is never explained (identifier format, accepted names), leaving half the parameters undocumented in both schema and description.

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 ('Write a managed world out') and immediately disambiguates the three output modes: to='source' overwrites the import origin, a .mcworld suffix produces a file, any other path produces a world folder. An agent can tell exactly what the tool produces without opening the schema.

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?

Explains which value of 'to' selects which behavior, which is the real usage decision for this tool, and notes that overwritten content is backed up. It does not explicitly contrast with siblings such as world_backup or structure_export, leaving the agent to infer the export-vs-backup boundary.

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