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

bedrock-map-builder-mcp

by xRookieFight

world_import

Copies a Minecraft world folder or .mcworld file into the builder while leaving the original unchanged; use export to write edits back.

Instructions

Copy a world into the builder: a world folder (for example one from world_list's client section) or a .mcworld file. The original stays untouched; use world_export to write changes back.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and usefully states that the original world stays untouched. However, it does not explain overwrite behavior, destination naming, permissions, or what the import returns.

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 two concise sentences with the core operation and source forms front-loaded. The world_export guidance is useful and no wording is wasted.

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 two-parameter import tool with no annotations and no output schema, the description covers the main source types and non-destructive behavior. It remains incomplete regarding the name parameter, overwrite behavior, and destination 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 description coverage is 0%, so the description must compensate. It explains the required source parameter well by listing world folder and .mcworld file forms, but it does not mention the optional name parameter or clarify its effect.

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 states a specific verb and resource: copy a world into the builder. It also distinguishes the operation from world_export by explaining that export is for writing changes back.

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?

It gives clear usage context by naming acceptable sources, including a world folder from world_list's client section or a .mcworld file. It also points to world_export for the complementary write-back workflow, though it does not explicitly state when not to use this tool.

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