Skip to main content
Glama

List the entities in an area

read_entities
Read-onlyIdempotent

Lists non-player entities inside a specified Minecraft bounding box, including mobs, item frames, armor stands, minecarts, boats, and items, with positions, UUIDs, names, and optional full SNBT data.

Instructions

Lists the entities whose position is inside the box: item frames, paintings, armor stands, mobs, minecarts, boats, items. For each: id, position, rotation, UUID, custom name, what it is tied to (lead) and its data as SNBT (shortened unless full: true). Players are not listed. The server saves first and the tool reads the saved entity files, so it changes nothing. Limited to maxEntities.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "read_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe opposite corner [x, y, z], inclusive
fromYesOne corner [x, y, z]
fullNoGive each entity its complete data. Default false (common fields only, shortened).
dimensionNoDimension. Default overworld.overworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, but the description adds real mechanism: the server saves first and the tool reads saved entity files, SNBT is shortened unless full:true, and results are capped at maxEntities. The cap's default and the behavior when it is exceeded are not disclosed, keeping this below a 5.

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 tight sentences, front-loaded with the scope, followed by return fields and behavioral caveats. No filler, and each clause carries information the agent needs.

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?

With no output schema, the description usefully enumerates returned fields (id, position, rotation, UUID, custom name, lead binding, SNBT data), which is what an agent needs to consume results. Remaining gaps are the maxEntities default and any pagination/truncation reporting when the cap is hit.

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%, so from/to/full/dimension semantics are already documented in structured fields, and the description mostly restates them (box containment, shortened SNBT unless full). It introduces maxEntities, which is not a schema parameter, without explaining its default or source.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Lists the entities whose position is inside the box") and enumerates the entity kinds covered (item frames, paintings, armor stands, mobs, minecarts, boats, items), which cleanly separates it from read_blocks and read_file siblings. An agent can identify the tool's job without opening the schema.

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?

The "Players are not listed" exclusion and the entity enumeration give clear context for when this tool applies versus block/file readers. It does not explicitly name an alternative for cases outside the box or for player data, so routing is inferred rather than stated.

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