Skip to main content
Glama

Clone a box

clone_region
DestructiveIdempotent

Copies a box of blocks so its lowest corner lands at target coordinates, overwriting the destination; container contents and sign text are omitted, and source/destination cannot overlap.

Instructions

Copy a box of blocks (types and states) so that its lowest corner lands at (dest_x, dest_y, dest_z), overwriting the destination. Container contents and sign text are not copied. Source and destination must not overlap. At most 32,768 blocks (plugin limit) and at most 100,000.

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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "z1": "<z1>",
      "x2": "<x2>",
      "y2": "<y2>",
      "z2": "<z2>",
      "dest_x": "<dest_x>",
      "dest_y": "<dest_y>",
      "dest_z": "<dest_z>"
    },
    "name": "clone_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1YesX of one corner of the box (inclusive).
x2YesX of the opposite corner (inclusive).
y1YesY of one corner of the box (inclusive).
y2YesY of the opposite corner (inclusive).
z1YesZ of one corner of the box (inclusive).
z2YesZ of the opposite corner (inclusive).
dest_xYesX where the box's lowest-X edge lands.
dest_yYesY where the box's bottom lands.
dest_zYesZ where the box's lowest-Z edge lands.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and readOnly=false; the description adds real signal beyond that by naming what is destroyed ("overwriting the destination") and what is deliberately excluded (container contents and sign text). The block limits add further operational context, though the trailing "at most 100,000" has no unit and reads as an unfinished clause.

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?

Three front-loaded sentences that lead with the operation and then the caveats; almost every clause earns its place. The final fragment ("and at most 100,000.") is truncated and slightly muddies an otherwise clean structure.

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 mutation semantics, exclusions, and limits for a 9-parameter destructive tool. What is missing is failure behavior (e.g., partial copy when overlap or limits are violated) and any permission or region-protection prerequisites.

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 all nine parameters already carry descriptions, including the dest_* anchoring language. The description's "lowest corner lands at (dest_x, dest_y, dest_z)" largely restates what the schema says per-field, 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?

"Copy a box of blocks (types and states)" gives a specific verb and resource, and the anchoring rule (lowest corner lands at dest) makes the operation concrete. It does not name or contrast with any sibling such as fill_region or edit_blocks, so an agent must infer differentiation from the name alone.

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 description supplies constraints (source/destination must not overlap, overwrite semantics, block caps) from which usage is implied, but it never states when to choose this over fill_region or edit_blocks, nor any prerequisite conditions. Guidance is implied rather than explicit.

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