Skip to main content
Glama

Copy an area

copy_blocks
DestructiveIdempotent

Copies a defined block region to a new location, optionally skipping air to preserve existing blocks, and snapshots the destination first for undo.

Instructions

Copies the box from..to so its lowest corner lands at destination (with /clone). skip_air keeps what is already at the destination where the source is air. Snapshots the destination first for undo.

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": {
      "from": "<from>",
      "to": "<to>",
      "destination": "<destination>"
    },
    "name": "copy_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe opposite corner [x, y, z], inclusive
fromYesOne corner [x, y, z]
skip_airNoDo not copy air. Default false.
dimensionNoDimension. Default overworld.overworld
destinationYesWhere the lowest corner of the copy goes [x, y, z]
skip_backupNoOnly for areas too big for an undo snapshot, after backup_world. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=true, so the description does not need to re-establish risk. It adds real value beyond them by disclosing the automatic undo snapshot of the destination and by naming backup_world as the escape hatch when the area is too large to snapshot.

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?

Three tight sentences, front-loaded with the core copy-and-place semantics before the two modifier behaviors and the backup disclosure. No filler and nothing re-stated from the schema.

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 6-parameter destructive mutation with no output schema, the description covers overwrite behavior, air handling, automatic snapshotting, and the large-area fallback. The dimension parameter and return behavior go unmentioned, but the schema documents the former and there is no output to explain.

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; the description earns extra by sharpening skip_air from the schema's terse "Do not copy air" into the precise behavior of keeping destination blocks where the source is air, and by clarifying that destination refers to the lowest corner rather than a center or opposite corner.

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?

Specific verb and resource ("Copies the box from..to") with the exact placement rule ("lowest corner lands at destination") and the underlying /clone mechanic. It implicitly separates itself from fill_blocks/place_blocks by describing a copy rather than a fill or placement, but never names an alternative explicitly.

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?

Usage context is limited to parameter-level conditions: skip_air for preserving existing destination blocks and skip_backup for oversized areas after backup_world. There is no explicit statement of when to prefer this over clear_blocks, fill_blocks, or export/import_schematic, so the agent must infer routing from sibling names alone.

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