Skip to main content
Glama

Fill boxes

fill_blocks
DestructiveIdempotent

Fills one or more Minecraft box regions with a chosen block in sequence, with replace, hollow, outline, keep, or destroy modes and undo snapshots.

Instructions

Fills one or more boxes with a block, in order. Boxes over 32768 blocks are split for you. mode: replace (default), hollow (walls, inside cleared), outline (walls only, inside kept), keep (only air is filled), destroy (drops items). replace_only limits it to one block or #tag. Snapshots the area 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": {
      "fills": "<fills>"
    },
    "name": "fill_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
fillsYes
dimensionNoDimension. Default overworld.overworld
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 declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds real value beyond that: the 32768-block auto-split threshold, the fact that destroy mode drops items, and that the area is snapshotted first for undo. It omits permission requirements and any note on what happens with skip_backup.

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?

The purpose and the auto-split caveat are front-loaded, then the mode table, then the undo-snapshot guarantee. Every clause carries information; there is no filler or repetition of 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 destructive, annotation-covered write tool with no output schema, the definition covers the key unknowns: ordering, size limits, mode effects, filtering, and undo backing. The remaining gap is that dimension scoping and skip_backup (the risky escape hatch for oversized areas) are left entirely to the schema.

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 67%, and the description compensates well for the weakest part: it gives per-value meaning for every mode enum entry (walls, inside cleared, inside kept, only air filled, drops items) which the schema supplies only as bare enum strings. It also clarifies replace_only semantics; from/to, dimension and skip_backup get no narrative treatment.

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?

"Fills one or more boxes with a block, in order" is a specific verb plus resource with a scope (one or more boxes, ordered). It is clearly distinct from clear_blocks, copy_blocks and place_blocks by name of action, though it never explicitly contrasts itself with those siblings.

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 mode list implies usage contexts (hollowing, outlining, air-only filling, destructive replacement), but there is no explicit "use this when / use place_blocks instead" guidance. An agent can infer intent from the mode semantics but must decide on its own between this and sibling write tools.

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