Skip to main content
Glama

Get entity attribute

get_entity_attribute
Read-onlyIdempotent

Retrieves the base and effective value of a living Minecraft entity's attribute, such as max health or movement speed, using its UUID and attribute name.

Instructions

Base and effective value of a living entity's attribute (e.g. max_health, movement_speed).

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>",
      "attribute": "<attribute>"
    },
    "name": "get_entity_attribute"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesEntity UUID, e.g. as returned by summon_entity or get_players.
attributeYesAttribute such as 'max_health', 'movement_speed', 'attack_damage' or 'scale'.

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's real contribution is the base-vs-effective distinction, which tells the agent that modifiers are reflected in one of the returned values — useful context beyond the annotations. It does not say what happens for non-living or invalid entities, or whether the effective value accounts for active effects, so it stops short of a 4.

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 tight sentence with the substantive detail (base and effective value) front-loaded and examples placed at the end where they cost least. Nothing is redundant or padded.

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 two-parameter read tool with a full output schema and complete annotation coverage, the description carries what it needs to. The only material gap is edge-case behavior — non-living entities or unknown attribute names — which an agent would likely want to know before calling.

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 coverage is 100% and both parameters are documented in the schema itself, including the UUID format and the attribute naming convention. The description's attribute examples duplicate those already in the schema, adding no new meaning about format, casing, or fallback behavior for unknown attributes. Baseline 3 is correct.

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 description names a specific resource — a living entity's attribute — and states exactly what is returned: both the base and the effective value, with concrete examples (max_health, movement_speed). It implicitly reads as the read counterpart to set_entity_attribute, though it never names that sibling to draw the contrast explicitly.

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?

There is no when-to-use guidance, no mention of alternatives such as get_entity for broader data, and no stated prerequisites. The only scoping signal is the phrase 'living entity', which the agent must infer limits applicability; nothing tells the agent when to reach for this versus another getter.

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