Skip to main content
Glama

Fill a box

fill_region
DestructiveIdempotent

Fill a rectangular box with a chosen block, replacing all existing contents, or use air to clear the area. Blocks are placed without physics, so sand and water stay put until nearby updates.

Instructions

Fill a box (corners inclusive, any order) with one block, replacing everything inside; use 'air' to clear an area. Refuses boxes larger than 100,000 blocks. Blocks are placed without physics, so sand does not fall and water does not flow until neighbours update.

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>",
      "block": "<block>"
    },
    "name": "fill_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).
blockYesBlock id such as 'minecraft:stone' or 'oak_planks' (the minecraft: namespace is optional).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (destructive=true, idempotent=true, readOnly=false), the description discloses two behaviors an agent could not otherwise know: the 100,000-block size cap that causes refusal, and the no-physics placement rule so sand/water don't cascade until a neighbour update. It also makes explicit that everything inside the box is overwritten, matching the destructive hint rather than contradicting it.

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 sentences, front-loaded with the core action, then the size limit, then the physics caveat. No repeated schema content and nothing obviously removable.

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 no explanation, and the annotations cover the safety profile. The description covers limits, mutation semantics, and physics; only failure modes for invalid block ids or out-of-bounds regions are left unstated.

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 coordinates and block-id format are already documented. The description nonetheless adds meaning: corner order is arbitrary (schema only labels one vs. opposite corner), and 'air' is a valid block value used to clear an area, which the schema does not hint at.

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?

"Fill a box (corners inclusive, any order) with one block, replacing everything inside" is a specific verb+resource with precise scope, and it clarifies the corners can be given in any order. It does not name any sibling (e.g. edit_blocks or clone_region), so the agent must infer the distinction from names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete secondary use case ("use 'air' to clear an area") and a hard refusal condition (boxes over 100,000 blocks), which tells the agent when the call will fail. It stops short of naming alternatives or excluding overlapping tools, so usage context is clear but not exhaustive.

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