Skip to main content
Glama
bedrock-map-builder-mcp

bedrock-map-builder-mcp

by xRookieFight

fill_container

Places specified items into a chest, barrel, shulker box, or other container block at a given position, optionally clearing existing contents—useful for loot rooms, kits, and rewards.

Instructions

Put items into a chest, barrel, shulker box or other container block: loot rooms, kit chests, rewards.

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": {
      "pos": "<pos>",
      "items": "<items>"
    },
    "name": "fill_container"
  }
}

Input Schema

NameRequiredDescriptionDefault
posYes
clearNo
itemsYes
dimensionNooverworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it omits the single most important trait: the schema default clear=true means existing container contents are wiped before filling. That destructive default is never stated. It also says nothing about what happens when items exceed the 54-slot cap or whether the target block must already exist.

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?

A single tight sentence front-loads the action and resource, then appends use cases. Nothing is padded, though the brevity is partly achieved by omitting information an agent actually needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with four parameters, a nested item schema, an enum dimension, and a destructive default, the definition is far too thin. No output schema exists to cover return behavior, and the description leaves the clear-on-fill behavior and slot semantics entirely unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters including a nested items array (item, amount, slot, name, lore) and a dimension enum, so the description needed to compensate. It only conveys the loose idea that items land in a container; it never explains slot targeting, stacking/amount semantics, lore/name, or cross-dimension addressing.

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?

The description gives a concrete verb ('Put items into') and a specific resource class ('a chest, barrel, shulker box or other container block'), which separates it from generic block-placement siblings like place_blocks or fill_region. It stops short of naming any sibling to contrast with, so a 4 rather than a 5.

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?

Three use cases (loot rooms, kit chests, rewards) sketch the intended scenario, which is genuinely helpful context. But there is no when-not guidance, no prerequisite (does the container block need to exist first?), and no indication of how this differs from place_blocks or fill_region for populating a structure.

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