Skip to main content
Glama

Find blocks, biomes, or structures

locate
Read-onlyIdempotent

Find the nearest Minecraft blocks, biomes, or structures by target and radius, searching around coordinates, a player, or world spawn.

Instructions

The nearest blocks, biomes, or structures of some kinds, nearest first. block takes keys or tags (minecraft:diamond_ore, #minecraft:logs, #minecraft:iron_ores) and reads only loaded chunks (those near players), 32 blocks around by default; unloadedChunks says how many in range it skipped. biome asks the world generator, so it reaches unexplored land, 1024 blocks around by default. structure takes keys such as stronghold, ancient_city, trial_chambers, or a prefix such as village that matches every village kind; radius is in chunks, and unexplored keeps only ones nobody found yet. Without x and z it searches around the player (the user's own when WORLDAPI_PLAYER is set), or, for biomes and structures, from the world spawn. Coordinates are private: it needs players:private, or anonymous access the server allows. Structure search blocks the server thread for a moment, so keep the radius modest.

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": {
      "kind": "<kind>",
      "targets": "<targets>"
    },
    "name": "locate"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoBlock X of the center
yNoNeeded for blocks when x and z are given
zNoBlock Z of the center
kindYesWhat targets name
limitNoResults to return, nearest first; 10 by default
worldNoWorld name; the player's world, or `world`, when left out
playerNoSearch around this player instead of x, y, z
radiusNoBlocks for blocks and biomes, chunks for structures
targetsYesSuch as ["minecraft:diamond_ore", "#minecraft:logs"], ["minecraft:cherry_grove"], or ["village"]
unexploredNoStructures only: only ones nobody has found yet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.2.1
    • addedInput schema / properties / kind / description
      Added value: +"What targets name"
    • addedInput schema / properties / x / description
      Added value: +"Block X of the center"
    • addedInput schema / properties / z / description
      Added value: +"Block Z of the center"
  2. First observedv4.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: block searches only read loaded chunks, structure search blocks the server thread so radius should stay modest, and coordinates require players:private or anonymous access. These are real operational constraints an agent cannot infer from the schema.

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?

One dense paragraph, front-loaded with the core behavior and then per-kind specifics, permissions, and the performance caveat. Every clause carries information, though the per-kind rules could be broken out for faster scanning.

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?

For a 10-parameter tool with no output schema, the description covers targeting, radius units, defaults, permission needs, and a performance warning. The notable gap is that it never says what a result looks like (coordinates, distance, world) despite there being no output schema to fall back on.

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 coverage is 100%, so baseline is 3; the description still adds value by showing tag syntax (`#minecraft:logs`), noting that structures accept prefixes like `village`, and clarifying that `unexplored` filters to undiscovered structures. It leaves `world` and `limit` untouched, but those are self-documented in the schema.

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 opening sentence names the resource set (blocks, biomes, structures) and the ordering guarantee (nearest first), which is enough to separate it from siblings like get_block, list_chunks, and find_containers. It is a noun phrase rather than a verb, but the intent is unambiguous.

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

Usage Guidelines4/5

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

It explains when each `kind` applies, the differing defaults per kind (32 blocks for blocks, 1024 for biomes, chunk radius for structures), and what happens when x/z are omitted (player or world spawn). It does not explicitly name alternative tools to use instead, so it stops short of a 5.

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