Skip to main content
Glama

Entity counts

get_entity_summary
Read-onlyIdempotent

Summarize loaded Minecraft entities or those within a radius, including totals, type counts, ground items, villagers, named mobs, tamed pets, and busiest chunks before listing entities individually.

Instructions

A compact look at a world's loaded entities, or those within radius of x, y, z: totals, counts by type, items on the ground, villagers, named mobs, tamed pets, and the ten busiest chunks with their block entities and hoppers. Call it before list_entities, which shows entities one by one.

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": "get_entity_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoCenter X
yNoCenter Y
zNoCenter Z
typesNoCount only these entity keys, such as ["minecraft:item"]
worldNoWorld name, such as `world`, `world_nether`, `world_the_end`, or a key like `minecraft:the_nether`world
radiusNoBlocks around x, y, z; give all three with it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.2.1
    • addedInput schema / properties / x / description
      Added value: +"Center X"
    • addedInput schema / properties / y / description
      Added value: +"Center Y"
    • addedInput schema / properties / z / description
      Added value: +"Center Z"
  2. First observedv4.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent operation, so the description need not repeat those traits. It adds useful behavioral context by enumerating the summary contents: totals, type counts, ground items, villagers, named mobs, tamed pets, and busiest chunks with block entities and hoppers. It does not discuss performance or limits, but the annotation coverage lowers the burden.

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 sentences with no wasted wording. The scope and return categories are front-loaded, and the sibling comparison is placed at the end where it is useful.

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?

For a read-only summary tool with a fully described schema and no output schema, the description is complete enough: it explains what the tool summarizes, how the radius scope works, and when to choose it over list_entities.

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 the schema already explains x, y, z, types, world, and radius. The description reinforces that radius requires x, y, and z and mentions type-based counting, but adds little beyond what the schema already documents, making 3 the appropriate baseline.

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?

The description names the specific resource (a world's loaded entities) and the precise scope (all loaded entities or those within a radius of x, y, z). It also distinguishes the tool from list_entities by contrasting summary counts with one-by-one entity listings.

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

Usage Guidelines5/5

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

It explicitly says to call this before list_entities and explains the distinction: this tool gives summary counts, while list_entities shows entities individually. That is clear routing guidance against a relevant sibling.

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