Skip to main content
Glama

Set entity attribute

set_entity_attribute
Idempotent

Set a living entity's base attribute value, such as max health or scale, by UUID to control gameplay stats and behavior.

Instructions

Set the base value of a living entity's attribute, e.g. max_health 40 or scale 2.

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>",
      "base_value": "<base_value>"
    },
    "name": "set_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'.
base_valueYesNew base value.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the operation is non-read-only, idempotent, non-destructive, and world-local, so the safety profile is covered. The description adds the meaningful nuance that it sets the *base* value on a *living* entity, but says nothing about persistence, whether the entity must be loaded, or what happens with an invalid attribute name.

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?

A single front-loaded sentence: verb, resource, qualifier ('base value'), then illustrative examples. Nothing is repeated and no sentence fails to earn its place.

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?

An output schema exists, so return values need no explanation, and annotations plus full schema coverage handle most of the burden. However, for a mutation tool the description leaves real gaps: whether modifiers are untouched, whether the entity must exist/be loaded, and error behavior on unknown attributes.

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 all three parameters are already documented in the schema itself, making 3 the baseline. The description's inline examples ('max_health 40 or scale 2') usefully show attribute/value pairing and reinforce the pattern already present in the schema, but add no new constraints or formats.

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?

States a specific verb and resource: 'Set the base value of a living entity's attribute', with concrete examples (max_health 40, scale 2) that make the operation unambiguous. It implicitly distinguishes itself from get_entity_attribute via the set/read split, but never names that sibling 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?

No guidance on when to use this versus get_entity_attribute for inspection or versus other set_entity_* mutators. The word 'base' hints at a distinction from attribute modifiers, but the description never says whether modifiers are preserved, so an agent must infer the intended scope.

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