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

bedrock-map-builder-mcp

by xRookieFight

structure_import

Places .mcstructure files into a Minecraft Bedrock world at a chosen origin, with optional rotation, mirroring, skip-air, undo, and preview-only rendering before writing.

Instructions

Place a .mcstructure file into the world at origin (its min corner), optionally rotated or mirrored. Structure void cells leave the world alone. preview_only renders it without writing.

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

Input Schema

NameRequiredDescriptionDefault
fileYes
undoNo
mirrorNonone
originNo
rotateNo
skip_airNo
dimensionNooverworld
preview_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does add genuinely useful behavior: void cells are skipped, and preview_only performs a non-writing render. It is silent on the mutation's side effects that matter most — whether existing blocks are overwritten, whether the default undo=true makes the operation revertible, and what the tool 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?

Three short sentences, front-loaded with the core action and its placement anchor, then behavior, then the preview switch. No filler and no repetition of the tool name.

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?

This is an 8-parameter mutating tool with no annotations and no output schema, so the description has to do heavy lifting. It covers placement semantics and void-cell behavior well but leaves the majority of parameters and the overwrite/undo consequences undocumented.

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%, so the description must explain all 8 params, but it only touches origin (min corner), rotate/mirror, and preview_only. Semantically significant ones like skip_air, dimension, and undo are never explained, leaving the agent to guess at air-block handling and target dimension.

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?

The description gives a specific verb and resource: 'Place a .mcstructure file into the world', and even clarifies what 'origin' means ('its min corner'). It does not contrast itself with plausible siblings such as world_import or structure_export, so an agent must infer the boundary from the name alone.

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 statement of when to prefer this tool over alternatives, no prerequisites (e.g. file must already exist or be uploaded), and no when-not guidance. The mention of preview_only hints at a dry-run workflow but never frames it as a decision rule.

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