Skip to main content
Glama

Import a .schem into the world

import_schematic
DestructiveIdempotent

Pastes a Sponge .schem into a Minecraft world at a chosen origin, restoring blocks, chests, signs, and entities, with optional area clearing and an undo snapshot.

Instructions

Pastes a Sponge schematic (.schem, version 2 or 3, as WorldEdit and most editors save) from the test server folder into the world with its lowest corner at origin, including chests, signs and other block data. include_air (default true) clears the area first so the result matches the file exactly. Snapshots the area first for undo. Entities in the file (item frames, paintings, armor stands, mobs, minecarts, boats) are summoned after the blocks, with fresh UUIDs; leads stay tied and riders stay seated. include_air also removes the entities already in the area. 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": {
      "file": "<file>",
      "origin": "<origin>"
    },
    "name": "import_schematic"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath inside the test server folder ending in .schem, for example "schematics/house.schem"
originYesWhere the lowest corner goes [x, y, z]
confirmNoSet true only after the person agreed to this change (needed while confirmDestructive is on).
dimensionNoDimension. Default overworld.overworld
include_airNoClear the area first so air in the file replaces what is there. Default true.
skip_backupNoOnly for areas too big for an undo snapshot, after backup_world. 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

A3.8/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and idempotentHint=true, so the safety profile is already known. The description does add destructive context beyond that: an undo snapshot is taken first, include_air clears the area, and include_air also removes entities already present. But it never explains what happens when maxImportBlocks/maxEntities is exceeded, whether a failed import leaves a partial state, or how confirm interacts with confirmDestructive; those are the operational details an agent needs before a destructive write.

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?

Front-loaded with what the tool does, then progressive detail on block data, include_air, undo, and entities. Every sentence carries a distinct fact; nothing is repeated from the schema or annotations.

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 a destructive, annotation-covered mutation with no output schema, this covers format, placement, entities, undo, and limits well. The remaining gap is failure behavior at the size caps and what the tool returns on success.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description goes further by explaining include_air's side effects on entities, tying 'snapshots the area first for undo' to skip_backup, and flagging the maxImportBlocks/maxEntities limits. It leaves confirm and dimension to the schema, which is acceptable since both are already documented there.

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?

Names a specific verb and resource (pastes a Sponge .schem file into the world at the lowest corner at origin) and pins down format support (.schem v2/v3 as WorldEdit saves it). It is clearly distinct from export_schematic, place_blocks and fill_blocks without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The when-to-use context is implied by the file-plus-origin framing, and there is real conditionality ('skip_backup only for areas too big for an undo snapshot, after backup_world') plus the confirm prerequisite. However, no alternative tool is ever named or excluded, so an agent must infer on its own why it would pick this over place_blocks or restore_world.

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