Skip to main content
Glama

fill_blocks

Fill a defined 3D region in Minecraft with blocks using coordinates and block IDs, supporting modes like replace, hollow, or outline for world editing.

Instructions

Fill a region with blocks. Uses the /fill command. Max 32,768 blocks per operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
x1YesStart X
y1YesStart Y
z1YesStart Z
x2YesEnd X
y2YesEnd Y
z2YesEnd Z
blockYesBlock ID
modeNoFill modereplace

Implementation Reference

  • The handler function for the fill_blocks tool which executes the fill command via RCON.
    async ({ x1, y1, z1, x2, y2, z2, block, mode }) => {
      try {
        const response = await manager.rcon.send(
          `fill ${x1} ${y1} ${z1} ${x2} ${y2} ${z2} ${block} ${mode}`
        );
        return { content: [{ type: "text", text: response }] };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Failed: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema for the fill_blocks tool.
    {
      x1: z.number().describe("Start X"),
      y1: z.number().describe("Start Y"),
      z1: z.number().describe("Start Z"),
      x2: z.number().describe("End X"),
      y2: z.number().describe("End Y"),
      z2: z.number().describe("End Z"),
      block: z.string().describe("Block ID"),
      mode: z
        .enum(["destroy", "hollow", "keep", "outline", "replace"])
        .optional()
        .default("replace")
        .describe("Fill mode"),
    },
  • Registration of the fill_blocks tool with the MCP server.
    server.tool(
      "fill_blocks",
      "Fill a region with blocks. Uses the /fill command. Max 32,768 blocks per operation.",
      {
        x1: z.number().describe("Start X"),
        y1: z.number().describe("Start Y"),
        z1: z.number().describe("Start Z"),
        x2: z.number().describe("End X"),
        y2: z.number().describe("End Y"),
        z2: z.number().describe("End Z"),
        block: z.string().describe("Block ID"),
        mode: z
          .enum(["destroy", "hollow", "keep", "outline", "replace"])
          .optional()
          .default("replace")
          .describe("Fill mode"),
      },
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses the hard limit (32,768 blocks) and identifies underlying mechanism ('/fill command'). Could improve by noting coordinate ordering flexibility or what happens when exceeding the limit.

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, zero waste: action statement, implementation detail, operational limit. Perfectly front-loaded with the core operation. No redundant information or verbose explanations.

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?

Appropriate for a 3D region operation with 8 parameters. With full schema coverage and no output schema, the description covers the essential constraint (block limit) and command context. Could mention that 'mode' affects existing blocks, but schema handles parameter details adequately.

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 has 100% description coverage (Start/End X/Y/Z, Block ID, Fill mode), so baseline 3 applies. Description adds minimal semantic value beyond schema, though 'region' subtly reinforces that coordinate pairs define a spatial volume.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Excellent specificity: 'Fill a region with blocks' provides clear verb (fill) and resource (region/blocks). The phrase 'region' effectively distinguishes this from the sibling tool 'set_block' (implied single block operation). Mentioning '/fill command' anchors it to Minecraft semantics.

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?

Provides critical constraint 'Max 32,768 blocks per operation' which informs usage limits. However, lacks explicit guidance on when to prefer this over 'set_block' or other building tools, and doesn't mention prerequisites like coordinate system knowledge.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tamo2918/Minecraft-Server-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server