Skip to main content
Glama

Locate structure

locate_structure
Read-onlyIdempotent

Finds the nearest Minecraft structure of a specified type in the main world, searching up to 100 chunks from coordinates or world spawn; may generate chunks.

Instructions

Find the nearest structure of a type in the main world, searching up to 100 chunks out. Can take a few seconds and may generate chunks.

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": {
      "structure": "<structure>"
    },
    "name": "locate_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoSearch from this X (with z); default: world spawn.
zNoSearch from this Z (with x); default: world spawn.
structureYesStructure id such as 'village_plains', 'minecraft:stronghold' or 'ancient_city'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds two genuinely useful behavioral facts: the call costs a few seconds and it may generate chunks as a side effect. Noting chunk generation is especially valuable given readOnlyHint=true, since it warns the agent the world state on disk can change. It leaves out what happens on a negative result.

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?

Two short sentences, front-loaded with what the tool does, followed by the cost and side-effect caveat. Nothing is repeated and nothing is wasted.

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

Completeness5/5

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

With only three fully documented parameters, an output schema for return values, and annotations covering the safety profile, the description supplies the remaining pieces an agent needs: search radius, latency expectation, and the chunk-generation side effect.

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%, and the schema already explains x/z as an optional search origin defaulting to world spawn and gives examples for the structure id. The description adds no parameter-level detail beyond that, so the baseline 3 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?

"Find the nearest structure of a type in the main world" gives a specific verb (find) plus resource (structure) and adds a concrete scope (nearest, up to 100 chunks). It doesn't explicitly contrast itself with place_structure or other siblings, so it falls just short of full differentiation.

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 agent can infer this is for locating structures when it knows the structure id, and the radius limit tells it what the search covers. There is no explicit when-to-use versus an alternative, and no mention of failure behavior when nothing is found within 100 chunks.

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