Skip to main content
Glama

Export an area to .schem

export_schematic
DestructiveIdempotent

Saves a selected box from..to as a Sponge .schem file with block states, chest/sign data, and entities so you can paste it on any WorldEdit server. Choose version 3 or 2 for compatibility.

Instructions

Saves the box from..to as a Sponge schematic (.schem) inside the test server folder, with block states and block data (chest contents, sign text). Version 3 (default) suits WorldEdit 7.3 and newer; use version 2 for older tools. The file can be pasted on any server with WorldEdit or a similar plugin. Entities whose position is inside the box (item frames, paintings, armor stands, mobs, minecarts, boats) are saved with all their data. Limited to maxImportBlocks and maxEntities.

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": "export_schematic"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes[x, y, z]
fileYesPath inside the test server folder ending in .schem, for example "schematics/house.schem"
fromYes[x, y, z]
confirmNoSet true only after the person agreed to this change (needed while confirmDestructive is on).
versionNoSponge schematic version, 3 (default) or 2
dimensionNoDimension. Default overworld.overworld
overwriteNoReplace a file that exists. Default false.
include_entitiesNoInclude entities (item frames, paintings, armor stands, mobs, minecarts, boats). Default: includeEntities in the config (on).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the write nature is already known; the description adds substantive behavior beyond that — what is captured (block states, chest contents, sign text, entity data), the hard limits maxImportBlocks/maxEntities, and where the file lands. It does not mention what happens when the target file already exists, leaving that to the overwrite param.

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?

The save action and destination are front-loaded, followed by version guidance, portability, entity scope, and limits in a tight sequence with no filler. It is five sentences, all of which carry information an agent needs.

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?

For an 8-parameter export tool with no output schema, the description covers format, contents, limits, and version choice well. Gaps remain around the return value (e.g. resulting path or block count), boundary inclusivity of the from/to box, and the overwrite/confirm interaction.

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 coverage is 100%, so the baseline is 3. The description does add genuine meaning for version by tying it to WorldEdit 7.3+ versus older tools, and it enumerates the entity types include_entities covers, but from/to, file, overwrite, and confirm get no added semantic detail.

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 gives a specific verb and artifact: 'Saves the box from..to as a Sponge schematic (.schem) inside the test server folder'. It also scopes the contents (block states, block data, entities), which distinguishes it clearly from the inverse import_schematic sibling.

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 supplies real selection guidance for the version parameter: 'Version 3 (default) suits WorldEdit 7.3 and newer; use version 2 for older tools', and explains the resulting file's portability. It stops short of explicit when-not guidance or noting the confirm/overwrite prerequisites, which the schema carries instead.

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