Skip to main content
Glama

Place jigsaw structure

place_jigsaw
Destructive

Generate a Minecraft jigsaw structure from a template pool, placing it at specified coordinates or at world spawn if coordinates are omitted.

Instructions

Generate a jigsaw structure from a template pool. Without coordinates it is placed at world spawn. Only dispatch is reported.

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": {
      "pool": "<pool>",
      "target": "<target>",
      "max_depth": "<max_depth>"
    },
    "name": "place_jigsaw"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoBlock X; give x, y and z together or leave all out.
yNoBlock Y; give x, y and z together or leave all out.
zNoBlock Z; give x, y and z together or leave all out.
poolYesJigsaw template pool such as 'minecraft:village/plains/town_centers'.
targetYesName of the jigsaw block to start from, e.g. 'minecraft:bottom'.
max_depthYesHow many jigsaw levels to expand (1-20).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds two useful facts beyond that: the fallback placement at world spawn and the limitation that 'Only dispatch is reported.' It still does not say what existing blocks or terrain get overwritten, which matters for a destructive placement tool.

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?

Two short sentences with no filler, and the core purpose is front-loaded. The phrase 'Only dispatch is reported' is slightly cryptic as written but is compact and relevant.

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?

With an output schema present, return values need not be described, and annotations carry the destructive/non-idempotent profile. The description covers the coordinate fallback and the reporting limitation, leaving only the extent of world mutation unstated, which is a modest gap for a 6-parameter destructive tool.

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 description coverage is 100% and each parameter (x/y/z grouping rule, pool example, target example, max_depth range) is already documented in the schema. The description adds no syntax or semantics beyond that, so the baseline of 3 applies.

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 and resource: 'Generate a jigsaw structure from a template pool.' That distinguishes it from generic siblings like place_structure or place_template by naming the jigsaw/template-pool mechanism. However, it never explicitly contrasts itself with place_structure or place_feature, so the differentiation is implied 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?

'Without coordinates it is placed at world spawn' describes a default behavior, not when to choose this tool over place_structure or place_feature. There is no when-to-use guidance, no prerequisites, and no named alternative for the obvious sibling candidates.

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