Skip to main content
Glama
bedrock-map-builder-mcp

bedrock-map-builder-mcp

by xRookieFight

list_entities

Read-only

Lists Minecraft Bedrock entities within a coordinate range or everywhere loaded, returning type, ID, name tag, position, and tags for inspection and analysis.

Instructions

Entities in a region (or everywhere loaded): type, id, name tag, position and tags.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
typeNo
limitNo
dimensionNooverworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

readOnlyHint=true already declares this a safe read, so the bar is lower. The description does add value by enumerating the returned fields (type, id, name tag, position, tags) in the absence of an output schema, but it says nothing about truncation: with a default limit of 200 and a cap of 2000, an agent has no warning that results may be silently capped.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, and the region scope is front-loaded. However, the brevity comes at the cost of under-specification rather than achieved conciseness, and the fragment structure makes it read as a data note rather than a tool description.

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

Completeness2/5

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

For a five-parameter tool with nested objects, 0% schema coverage, and no output schema, one fragment is not enough. The return fields are covered, but the filter parameters, region boundary semantics, and result-cap behavior are all left for the agent to guess.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, including two nested x/y/z objects, so the description must compensate and largely fails. 'Region' hints at from/to, but corner semantics and inclusivity are unstated; the `type` parameter is never mentioned and is confusingly shadowed by 'type' in the output field list; `dimension` and `limit` are not addressed at all.

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

Purpose3/5

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

The fragment 'Entities in a region (or everywhere loaded)' identifies the resource but never states a verb, so an agent must infer that this is a listing/query operation. The trailing field list ('type, id, name tag, position and tags') clarifies what is returned, which is helpful, but the sentence is a noun phrase rather than a purpose statement and does nothing to distinguish it from siblings like find_blocks or region_stats.

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

Usage Guidelines2/5

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

The parenthetical '(or everywhere loaded)' implies the region is optional, which is the only usage signal present. There is no explicit when-to-use, no when-not-to-use, and no named alternative for entity lookup versus block search or region stats.

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