Skip to main content
Glama

Change an entity

update_entity

Change a non-player Minecraft entity’s name, AI, glowing, gravity, invulnerability, health, fire, teleport, velocity, persistence, silence, or scoreboard tags.

Instructions

Rename, toggle AI, glowing, gravity, invulnerability, set health or fire, teleport, push, or tag an entity. Not for players.

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

Input Schema

NameRequiredDescriptionDefault
aiNoLiving entities only
uuidYesEntity UUID
worldNoWorld name, such as `world`, `world_nether`, `world_the_end`, or a key like `minecraft:the_nether`world
formatNo`minimessage` reads tags like `<green>Hi` or `<bold>`; `plain` sends the text as isplain
healthNoLiving only; 2 per heart, up to its max
silentNoNo sounds
addTagsNoScoreboard tags
glowingNoGlowing outline
gravityNofalse floats
locationNoTeleport here
velocityNoBlocks per tick; y is up
fireTicksNo20 per second; 0 puts it out
customNameNoName tag
persistentNoNever despawns
removeTagsNoScoreboard tags
invulnerableNoTakes no damage
customNameVisibleNoName always shown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv4.2.1
    • addedInput schema / properties / addTags / description
      Added value: +"Scoreboard tags"
    • addedInput schema / properties / ai / description
      Added value: +"Living entities only"
    • addedInput schema / properties / customName / description
      Added value: +"Name tag"
    • addedInput schema / properties / customNameVisible / description
      Added value: +"Name always shown"
    • addedInput schema / properties / fireTicks / description
      Added value: +"20 per second; 0 puts it out"
    • addedInput schema / properties / glowing / description
      Added value: +"Glowing outline"
    • addedInput schema / properties / gravity / description
      Added value: +"false floats"
    • addedInput schema / properties / health / description
      Added value: +"Living only; 2 per heart, up to its max"
    • addedInput schema / properties / invulnerable / description
      Added value: +"Takes no damage"
    • addedInput schema / properties / persistent / description
      Added value: +"Never despawns"
    • addedInput schema / properties / removeTags / description
      Added value: +"Scoreboard tags"
    • addedInput schema / properties / silent / description
      Added value: +"No sounds"
    • addedInput schema / properties / uuid / description
      Added value: +"Entity UUID"
    • addedInput schema / properties / velocity / description
      Added value: +"Blocks per tick; y is up"
  2. First observedv4.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is known; the description adds only the segmentation boundary. It does not disclose whether omitted fields are left untouched (partial-update semantics), what happens if the uuid does not resolve, or whether values like health above max are clamped — meaningful gaps for a 17-parameter mutation tool.

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?

One sentence, no boilerplate, with the most important scoping constraint ('Not for players') placed last where a reader will hit it before calling. The verb-list phrasing is dense enough to require a second read, but nothing is wasted.

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?

There is no output schema, so the description should say what comes back and whether the mutation is partial or total; neither is covered. Against a 17-parameter schema with nested location/velocity objects, the description is adequate to identify the tool but leaves enough behavioral ambiguity that an agent could mis-call it on a non-living entity or expect a full-state replace.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description earns above baseline by mapping intent verbs onto parameters the schema only names — 'rename' to customName, 'teleport' to location, 'push' to velocity, 'tag' to addTags/removeTags, 'set health or fire' to health/fireTicks. It omits silent, persistent, customNameVisible, format and world, but the intent-to-parameter mapping adds real value the schema does not provide.

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 opens with a dense but specific list of mutations (rename, toggle AI/glowing/gravity/invulnerability, set health/fire, teleport, push, tag) that together define the tool as an in-place entity attribute editor, and 'Not for players' cleanly separates it from set_player_property and teleport_player. It is not a single crisp verb+resource statement, but the enumerated capabilities leave no ambiguity about scope.

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

Usage Guidelines3/5

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

The negative boundary 'Not for players' is genuinely useful routing information, since sibling tools set_player_property and teleport_player exist. However, it names no alternative for players and gives no prerequisites (entity must be loaded/spawned, uuid must come from list_entities), so usage is only implied.

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