Skip to main content
Glama

Change a player

set_player_property

Change an online Minecraft player's game mode, health, hunger, XP, flight, speed, names, invulnerability, fire, or air. Use for player stat and setting updates while they are connected.

Instructions

Set game mode, health, food (0–20), saturation, XP level or progress, flight, walk or fly speed (-1 to 1; defaults 0.2 and 0.1), display or tab-list name, invulnerability, fire, or air; for position, effects, or items use teleport_player, set_effects, or edit_items. The player must be online; otherwise the error is player_offline.

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": {
      "player": "<player>"
    },
    "name": "set_player_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
expNoProgress to the next level
foodNoHunger bar
levelNoXP level
flyingNoNeeds allowFlight
formatNo`minimessage` reads tags like `<green>Hi` or `<bold>`; `plain` sends the text as isplain
healthNo2 per heart, up to the max; 0 kills
playerYesPlayer name or UUID
flySpeedNo0.1 is normal
gameModeNoGame mode
listNameNoName in the tab list
fireTicksNo20 per second; 0 puts it out
walkSpeedNo0.2 is normal
exhaustionNoAt 4, costs a point of saturation or food
saturationNoSpent before food
allowFlightNoMay fly
displayNameNoName in chat
invulnerableNoTakes no damage
remainingAirNoTicks, up to the max (300 by default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv4.2.1
    • addedInput schema / properties / allowFlight / description
      Added value: +"May fly"
    • addedInput schema / properties / displayName / description
      Added value: +"Name in chat"
    • addedInput schema / properties / exhaustion / description
      Added value: +"At 4, costs a point of saturation or food"
    • addedInput schema / properties / fireTicks / description
      Added value: +"20 per second; 0 puts it out"
    • addedInput schema / properties / flySpeed / description
      Added value: +"0.1 is normal"
    • addedInput schema / properties / flying / description
      Added value: +"Needs allowFlight"
    • addedInput schema / properties / food / description
      Added value: +"Hunger bar"
    • addedInput schema / properties / gameMode / description
      Added value: +"Game mode"
    • addedInput schema / properties / health / description
      Added value: +"2 per heart, up to the max; 0 kills"
    • addedInput schema / properties / invulnerable / description
      Added value: +"Takes no damage"
    • addedInput schema / properties / level / description
      Added value: +"XP level"
    • addedInput schema / properties / listName / description
      Added value: +"Name in the tab list"
    • addedInput schema / properties / remainingAir / description
      Added value: +"Ticks, up to the max (300 by default)"
    • addedInput schema / properties / saturation / description
      Added value: +"Spent before food"
    • addedInput schema / properties / walkSpeed / description
      Added value: +"0.2 is normal"
  2. First observedv4.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 a non-read-only, non-idempotent, non-destructive mutation, so the safety bar is partially met. The description adds real value beyond that: the online-player precondition and the literal `player_offline` error, plus that health=0 kills and fireTicks=0 extinguishes fire. It stops short of saying whether omitted properties are left untouched or whether permissions are required.

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?

Two sentences, front-loaded with the capability list followed by the routing alternatives and then the precondition. The property list is dense and long but every clause names a distinct capability; nothing is filler.

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 an 18-parameter mutation with no output schema, the description covers scope, sibling routing, and the key failure mode, while the schema fully documents parameter meaning. Missing only marginal context: whether unspecified properties are preserved, permission requirements, and any confirmation/return behavior.

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% and the schema already documents every one of the 18 parameters, including the 0.1/0.2 normal-speed values and the food 0-20 bound that the description restates. The description adds grouping and a quick scan but little semantic detail the schema lacks, so baseline 3 applies.

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?

States a specific verb and resource and then enumerates the exact settable properties (game mode, health, food, saturation, XP, flight/speeds, names, invulnerability, fire, air). It actively distinguishes itself from the sibling mutators it shares scope with, so an agent can route without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit exclusions with named alternatives: position -> teleport_player, effects -> set_effects, items -> edit_items. It also states the precondition for use (player must be online) and the error surfaced when it is not.

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