Skip to main content
Glama

Place structure template

place_template
DestructiveIdempotent

Place a saved structure template in a Minecraft world with its lowest corner at the given coordinates, supporting rotation, mirroring, and integrity options for ruined placement.

Instructions

Place a saved structure template (structure block / NBT file) with its lowest corner at (x, y, z). Only dispatch is reported; verify with get_blocks.

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": {
      "template": "<template>",
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "place_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesBlock X coordinate (east is +X).
yYesBlock Y coordinate (height; the overworld build range is -64 to 319).
zYesBlock Z coordinate (south is +Z).
seedNoSeed that picks which blocks integrity drops.
mirrorNoMirroring.none
rotationNoRotation.none
templateYesStructure template id such as 'minecraft:igloo/top' or a saved structure 'mymap:house'.
integrityNoFraction of blocks to place (below 1 gives a ruined look).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is largely covered. The description adds one genuinely useful, non-obvious disclosure: 'Only dispatch is reported', which tells the agent the call succeeding does not guarantee the world changed. It still never states that existing blocks at the target volume are overwritten, which is the key consequence implied by destructiveHint=true.

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?

Two short sentences, zero filler, with the placement semantics front-loaded and the verification caveat trailing. Nothing could be removed without losing information.

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?

An output schema exists, so return values need no explanation, and the description covers the anchor semantics plus the dispatch-only caveat. For an 8-parameter destructive world mutation, the only real omissions are overwrite behavior on the target region and differentiation from the sibling placement tools.

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 the baseline would be 3, but the description adds meaning the schema does not: the coordinates anchor the template's *lowest corner*, not its center or origin. That single clause materially changes how an agent computes x/y/z, which is more than the schema's per-field axis notes convey.

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 names a specific verb and resource ('Place a saved structure template (structure block / NBT file)') and pins down the anchor point with 'its lowest corner at (x, y, z)'. It is clear on its own, but it does nothing to separate itself from the very similar sibling 'place_structure' (or 'place_feature'/'place_jigsaw'), leaving the agent to guess which placement tool to pick.

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 instruction 'verify with get_blocks' gives a concrete follow-up step and points at a sibling, which is real usage guidance. However, there is no when-to-use/when-not guidance relative to 'place_structure', and no statement of prerequisites (e.g., whether the template must already exist or be loaded).

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