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

bedrock-map-builder-mcp

by xRookieFight

structure_export

Exports a defined world region to a .mcstructure file compatible with structure blocks and /structure load for reuse.

Instructions

Save a region of the world as a .mcstructure file (the format structure blocks and /structure load use).

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": {
      "from": "<from>",
      "to": "<to>",
      "file": "<file>"
    },
    "name": "structure_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fileYes
fromYes
dimensionNooverworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations are empty, so the description carries the full burden. It signals a file-writing mutation, but says nothing about where the file lands, whether existing files are overwritten, whether the server needs to be running, size or chunk limits, error behavior, or whether air blocks are included in the saved region.

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?

A single front-loaded sentence with zero filler; the format detail is useful and compactly parenthesized. It is efficient, though its brevity is achieved by omitting content rather than by tight editing of richer content.

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 tool with nested coordinate objects, an enum dimension, no annotations, no output schema, and zero schema descriptions, the one-sentence description is far too thin. An agent could not confidently call this correctly without guessing at coordinate ordering, path semantics, and dimension scope.

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% and the description mentions none of the four parameters. Critical semantics are left undefined: are 'from' and 'to' inclusive corners, does order matter, is 'file' an absolute path or a name resolved by the server, and what does the 'dimension' enum (default overworld) actually affect. The phrase "region of the world" only loosely maps to from/to.

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?

States a specific verb ("Save") and resource ("a region of the world") plus the exact output artifact (.mcstructure), which is enough to distinguish it from siblings like structure_import or world_export. It stops short of naming the importing counterpart, so the differentiation is inferred rather than stated.

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 when-to-use guidance, no mention of when to prefer structure_import, world_export, or copy_region instead, and no prerequisites. The parenthetical about structure blocks and /structure load hints at downstream consumption of the file but does not tell the agent when to pick this tool.

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