Skip to main content
Glama

Fill biome

fill_biome
DestructiveIdempotent

Changes the biome of a defined box in the main Minecraft world, affecting grass/water colors, weather, and mob spawns. Refuses boxes over 100,000 blocks and only reports command dispatch.

Instructions

Change the biome of a box in the main world (affects grass/water colour, weather and mob spawns; players may need to rejoin to see colours change). Refuses boxes over 100,000 blocks; the plugin only reports whether the vanilla /fillbiome command was dispatched.

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>",
      "biome": "<biome>"
    },
    "name": "fill_biome"
  }
}

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).
biomeYesBiome id such as 'minecraft:plains', 'desert' or 'cherry_grove'.
replace_biomeNoOnly replace this biome or #tag (e.g. 'plains' or '#minecraft:is_forest').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the supplied annotations. It adds a hard rejection rule ('refuses boxes over 100,000 blocks'), a critical observability caveat ('the plugin only reports whether the vanilla /fillbiome command was dispatched' - i.e. success does not mean the biome actually changed), and a client-side lag note about rejoining. For a destructive mutation tool these are exactly the traits an agent needs.

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?

Two sentences, no preamble, the primary action and its visible effects come first, followed by the two operational caveats. The parentheticals and semicolons make it dense, but every clause carries information an agent would otherwise get wrong.

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, yet the description still usefully flags that the return only reports command dispatch rather than verified effect. Combined with the size cap and rejoin note, coverage is strong for an 8-parameter mutation. The remaining gap is permission/authorization requirements, which are unmentioned.

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 description coverage is 100%, so the baseline would be 3. The description earns above baseline by introducing a derived constraint not expressible in the schema: the 100,000-block volume cap on the coordinate box, which changes how an agent should size x1..z2. It does not add anything about biome id or replace_biome syntax, which the schema already handles.

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 plus resource plus scope: 'Change the biome of a box in the main world.' An agent can immediately tell this alters biome data rather than blocks (fill_region/edit_blocks) or entities. It stops short of naming a sibling explicitly, so the differentiation comes from the resource noun 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?

Usage is implied rather than stated: the mention of grass/water colour, weather and mob spawns tells an agent why it would call this, and 'main world' scopes out other dimensions. But there is no explicit when-to-use/when-not guidance, no prerequisites (e.g. operator permission), and no pointer to alternatives for block-layer edits.

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