Skip to main content
Glama

Get entity

get_entity
Read-onlyIdempotent

Retrieve a Minecraft entity’s type, name, world, position, rotation, velocity, health, and AI state using its UUID for inspection or tracking.

Instructions

Details of one entity: type, custom name, world, position, rotation, velocity, health and AI state.

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": {
      "uuid": "<uuid>"
    },
    "name": "get_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesEntity UUID, e.g. as returned by summon_entity or get_players.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety and repeatability are fully covered by structured data. The description adds only the set of populated fields, which the output schema largely restates. It says nothing about error behavior for an unknown or unloaded UUID, though with no mutation risk this is a minor omission.

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?

A single front-loaded sentence with no filler. The enumeration of return fields is somewhat redundant against the output schema, which is the only thing keeping it from a perfect score.

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

Completeness3/5

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

Annotations cover the safety profile, the input schema fully covers the single parameter, and an output schema exists so return values need no explanation. The missing piece is routing guidance against the many sibling entity getters/setters and any note about behavior on an invalid or nonexistent UUID.

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?

There is one required parameter, uuid, with a fully described schema including a regex pattern and an example of its provenance. The description adds no semantics beyond that; baseline 3 applies because the schema covers parameter meaning completely.

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?

"Details of one entity" names a specific resource and scope, and the field list (type, custom name, world, position, rotation, velocity, health, AI state) makes clear this is the broad snapshot getter rather than a narrow one like get_entity_attribute or get_entity_equipment. It stops short of explicitly contrasting itself with those siblings, so an agent must infer the distinction from field names.

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 description gives no when-to-use guidance, no prerequisites, and no alternatives. It never mentions get_entity_attribute, get_entity_equipment, or get_players, even though the schema hint shows the UUID can come from summon_entity or get_players. Usage is only implied by the word "Details".

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