Skip to main content
Glama

Change potion effects

set_effects

Give, remove, or clear a Minecraft player's potion effects and return the effects they have afterward. Requires the player to be online.

Instructions

Give, take away, or clear a player's potion effects, in that order: clear first, then remove, then add. Answers with the effects the player has afterwards. 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_effects"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNoEffects to give
clearNoTake away every effect first
playerYesPlayer name or UUID
removeNoEffect keys to take away

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.2.1
    • addedInput schema / properties / add / description
      Added value: +"Effects to give"
  2. First observedv4.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare it mutates and is non-idempotent; the description adds genuinely new behavior: the deterministic ordering of clear/remove/add, the post-state return value ("the effects the player has afterwards"), and the specific `player_offline` error. It still doesn't say whether re-adding an existing effect replaces or stacks it, which matters given idempotentHint=false.

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?

Two tight sentences with no filler: the first front-loads the three operations and their order, the second covers return value and the failure mode. Every clause carries information an agent needs.

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?

With no output schema, the description correctly states what comes back, and it names the key error case. Coverage is complete for selection and invocation; only edge behavior (overwriting an existing effect) is unstated.

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 baseline is 3, but the description adds real semantics the schema cannot express: the precedence (clear, then remove, then add) that determines the final state when parameters overlap. That is a meaningful lift above the structured fields.

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 states a specific verb set and resource: "Give, take away, or clear a player's potion effects." The player-scoped framing implicitly separates it from the world-level sibling `world_effect`, but no sibling is ever named, so the differentiation is left to inference.

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

Usage Guidelines4/5

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

It gives a clear operational rule: the three operations apply "in that order: clear first, then remove, then add," which tells the agent exactly how to combine them. It also supplies a precondition (the player must be online). It stops short of naming alternatives or describing when not to use the tool.

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