Skip to main content
Glama
Sign In
Minecraft Structure Lab

Minecraft Structure Lab

by ewitulsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

generate_example_house

Generate a furnished house NBT structure fixture with selectable revision, saving to your specified output path.

Instructions

Generate the furnished house fixture. Revision 2 removes the gold sentinel and changes bedroom carpet.

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": {
      "output_path": "<output_path>"
    },
    "name": "generate_example_house"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionNo
output_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.3/5.0
Behavior2/5

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

The description reveals one behavioral detail: revision 2 removes the gold sentinel and changes bedroom carpet. However, it does not explain broader side effects, required permissions, destructive potential, or what 'generate' entails beyond this revision-specific note.

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?

The description is brief and free of redundant phrasing, making it easy to read. It is not overly verbose, though it could be slightly clearer by avoiding the somewhat vague term 'furnished house fixture.'

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

Completeness1/5

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

With no annotations, no output schema, and no parameter descriptions, the description leaves many essential details unspecified. An agent would likely have to infer how to call this tool correctly, what the output looks like, and how it differs from sibling tools.

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

Parameters1/5

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

The schema has two parameters with zero description coverage. The revision parameter is partially explained by the revision-2 note, but output_path is entirely unexplained, and no parameter-level details such as format, allowed values, or behavior are provided.

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 identifies a specific action ('Generate') and a clear resource ('the furnished house fixture'), which is more specific than a generic verb. However, it does not explicitly distinguish this from the sibling 'generate_structure' tool, leaving some ambiguity about when each is appropriate.

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

Usage Guidelines1/5

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

No guidance is provided about when to use this tool versus alternatives such as 'generate_structure' or other sibling tools. The description does not mention prerequisites, context, or conditions under which this tool should be selected.

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

Deploy Server

Other Tools