Skip to main content
Glama

Place feature

place_feature
Destructive

Generates a configured world feature such as a tree, ore vein, or dungeon at specified coordinates or at world spawn when coordinates are omitted; reports only whether the command was dispatched.

Instructions

Generate a configured feature (tree, ore vein, dungeon, ...) like world generation does. Without coordinates it is placed at world spawn. Only whether the command was dispatched is reported.

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": {
      "feature": "<feature>"
    },
    "name": "place_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoBlock X; give x, y and z together or leave all out.
yNoBlock Y; give x, y and z together or leave all out.
zNoBlock Z; give x, y and z together or leave all out.
featureYesConfigured feature id such as 'minecraft:oak', 'fancy_oak' or 'monster_room'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive=true, non-idempotent, and non-read-only, so the safety profile is covered; the description adds genuinely new behavior by warning that only command dispatch is reported, meaning no success confirmation comes back. It also discloses the fallback placement at world spawn, a side effect an agent could not get from the schema. It does not explain what making it destructive actually does to existing blocks.

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 short sentences, zero filler, with the operation stated first, the placement fallback second, and the limited reporting caveat last. Every sentence earns its place.

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, so return values need not be itemized, and the description still flags that the response confirms only dispatch. For a destructive world-mutating tool the one remaining gap is a note on what gets overwritten or whether the target chunk must be loaded, but overall it is sufficient to call correctly.

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 description coverage is 100%, with each coordinate carrying its own 'give x, y and z together or leave all out' note and the feature parameter carrying an id format and examples. The description only restates the all-or-nothing coordinate rule; the 3-parameter baseline applies.

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?

States a specific verb and resource ('Generate a configured feature') and gives concrete examples (tree, ore vein, dungeon) plus the notion that it mirrors world generation, which separates it conceptually from place_structure and place_jigsaw. It stops short of naming a sibling or explicitly contrasting with structure/template placement, so the differentiation is implied rather than stated.

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 description covers the coordinate-omitted case ('placed at world spawn'), which is real usage context, but never says when to prefer this over place_structure, place_jigsaw, or place_template. An agent must infer the choice from the words 'configured feature' alone.

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