Skip to main content
Glama

Export a design as a game file

export
Read-onlyIdempotent

Turn a design into a file the user loads in Minecraft Java Edition 26.3, so they need not place every block by hand: format "nbt" is the vanilla structure file (load it with a structure block or /place template, no mods), "schem" a Sponge schematic (WorldEdit, Litematica). Give either design or example. The file comes back as an embedded resource; the viewer from show also has a download button. Use it when the user wants to build the machine in their world. Do not use it to test a design: use simulate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export"
  }
}

Input Schema

NameRequiredDescriptionDefault
designNoA machine: a list of blocks plus what it is for. See the server instructions for block types and rules.
formatNoschem (WorldEdit, Litematica; the default) or nbt (vanilla structure file)
exampleNoId of a built-in example to export instead of a design

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / design / properties / test / properties / inputs / description
      Previous value: -"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), strike (lightning strikes a lightning rod), turn_page (lectern), open and close (chest or trapped chest; for stand, leave, open and close an optional player 1-4, default 1), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"New value: +"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), strike (lightning strikes a lightning rod), turn_page (lectern), open and close (chest or trapped chest; for stand, leave, open and close an optional player 1-4, default 1), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a plain minecart on a rail; a hopper minecart goes in the design: \"minecart\": \"hopper\" on the rail)"
  2. Changed1 schema field changed
    • changedInput schema / properties / design / properties / test / properties / inputs / description
      Previous value: -"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), strike (lightning strikes a lightning rod), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"New value: +"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), strike (lightning strikes a lightning rod), turn_page (lectern), open and close (chest or trapped chest; for stand, leave, open and close an optional player 1-4, default 1), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"
  3. Changed1 schema field changed
    • changedInput schema / properties / design / properties / test / properties / inputs / description
      Previous value: -"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"New value: +"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), strike (lightning strikes a lightning rod), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"
  4. Changed1 schema field changed
    • changedInput schema / properties / design / properties / test / properties / inputs / description
      Previous value: -"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame or cake; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"New value: +"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame, cake or jukebox; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"
  5. Changed1 schema field changed
    • changedInput schema / properties / design / properties / test / properties / inputs / description
      Previous value: -"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor or fence gate; optional look), stand (step onto a pressure plate or string), leave (step off), throw (a snowball at a target), turn_page (lectern), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"New value: +"What a player does: {tick, do, at: [x,y,z]}. do: pull (lever), press (button), use (wooden door, wooden trapdoor, fence gate, note block, bell, redstone ore, item frame or cake; optional look), stand (step onto a pressure plate, string or redstone ore), leave (step off), throw (a snowball at a target), turn_page (lectern), open and close (chest or trapped chest), toggle (daylight detector), start (place a block against the observer marked \"start\": true; no at), place_cart (put a minecart on a rail)"
  6. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, so the description's added context is what counts here: it discloses how the artifact is delivered ('comes back as an embedded resource', also downloadable from the show viewer) and what each format requires to load. It stops short of stating limits, validation, or what happens when neither design nor example is supplied.

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?

Purpose is front-loaded in the first clause and every sentence carries information; nothing is filler. It is a dense single block, though, with the format definitions and delivery mechanics packed mid-paragraph, and would scan faster as short bullets.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with a deeply nested input schema and no output schema, the description covers the pieces that matter: the two formats and their load paths, the choice between 'design' and 'example', the shape of the return value, and the sibling boundary against 'simulate'. What remains unspecified (behavior when both inputs are omitted) is an edge case rather than a blocker.

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 3 is the baseline, but the description adds real meaning: it explains the practical consequences of the 'format' enum ('no mods', /place template vs WorldEdit/Litematica) and imposes an input constraint the schema does not encode ('Give either design or example').

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?

States a specific verb and resource (turn a design into a loadable game file) and immediately scopes it with the concrete target ('Minecraft Java Edition 26.3'). It also distinguishes itself from siblings by naming 'simulate' as the tool for testing, so an agent can pick between the two without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use condition ('the user wants to build the machine in their world') and an explicit when-not with the alternative named ('Do not use it to test a design: use simulate'). It further routes file-format choice by naming the downstream consumers (structure block/place template vs WorldEdit/Litematica).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources