Skip to main content
Glama

Set entity equipment

set_entity_equipment
DestructiveIdempotent

Equip a living entity (mob or armor stand) with items in chosen slots; omitted slots remain unchanged and replaced items are lost.

Instructions

Equip a living entity (mob or armor stand); slots you omit are left unchanged, and the replaced items are lost.

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

Input Schema

NameRequiredDescriptionDefault
uuidYesEntity UUID, e.g. as returned by summon_entity or get_players.
bootsNoItem id for this slot ('air' empties it).
helmetNoItem id for this slot ('air' empties it).
leggingsNoItem id for this slot ('air' empties it).
off_handNoItem id for this slot ('air' empties it).
main_handNoItem id for this slot ('air' empties it).
chestplateNoItem id for this slot ('air' empties it).
drop_chancesNoChance (0-1) that each slot's item drops when the mob dies.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description supplies the concrete consequence an agent needs: partial-update semantics plus 'the replaced items are lost'. That gives real content about what the mutation destroys beyond a generic destructive flag. It stops short of saying whether permissions are required or what the response contains, but the output schema covers returns.

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 sentence with two clauses that each carry information: the target scope comes first, then the update/loss semantics. No padding, no restatement of the title, and the most important constraint is front-loaded.

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?

The tool is a targeted mutation with a rich schema (100% coverage, all slots described) and a declared output schema, so the description only needs to carry the intent and the loss/partial-update semantics, both of which it does. Read/write separation is handled by the sibling get_entity_equipment and safety profile by the annotations.

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 the schema already documents every slot; the description still adds non-trivial meaning by stating 'slots you omit are left unchanged'. That resolves an ambiguity the schema leaves (default null alongside "'air' empties it") without the agent having to guess whether omission or null clears a slot. It does not explain item-id format or drop_chances behavior, so it is useful rather than complete.

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 opens with a specific verb+resource pair, 'Equip a living entity (mob or armor stand)', which tells the agent exactly what is written and to which target class. The parenthetical narrows the domain enough to distinguish it from other entity mutators like set_entity_attribute or set_entity_ai without needing another schema.

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 description makes an implicit use case clear (modifying the equipment of an existing living entity) and the 'living entity (mob or armor stand)' qualifier hints that non-living or non-mob entities are out of scope. However, it never says when to prefer this over get_entity_equipment for reads, or warns against using it on players, so the reader must infer the boundary.

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