Skip to main content
Glama

Apply status effect

apply_effect
Idempotent

Gives an online Minecraft player a chosen status effect, such as speed or regeneration, with optional duration, amplifier, and particle settings.

Instructions

Give an online player a status effect such as speed, night_vision or regeneration.

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": {
      "username": "<username>",
      "effect": "<effect>"
    },
    "name": "apply_effect"
  }
}

Input Schema

NameRequiredDescriptionDefault
effectYesStatus effect id such as 'speed', 'night_vision' or 'minecraft:regeneration'.
usernameYesExact, case-sensitive name of an online player.
amplifierNo0 = level I, 1 = level II, ...
hide_particlesNoHide the effect's particles.
duration_secondsNoDuration in seconds.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare non-readOnly, idempotent, non-destructive, non-openWorld behavior, so the safety profile is covered. The description adds only the implicit online-player requirement; it does not say whether re-applying replaces or stacks an existing effect of the same type, nor whether duration is capped in practice.

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?

A single front-loaded sentence with zero filler, so nothing is wasted. It is arguably over-trimmed, since the space saved could have carried routing or precondition detail.

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?

With 5 parameters fully documented in the schema, annotations covering the mutation profile, and an output schema present, most of the agent's needs are met elsewhere. The gap is behavioral: nothing explains effect replacement/stacking semantics or the offline-player failure mode.

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%, with effect ids, amplifier levels, particle hiding and duration all documented in the schema itself, including the namespaced id pattern. The description's examples of effect ids merely restate what the effect property already shows, adding no new parameter meaning.

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+resource ('Give ... a status effect') with concrete examples (speed, night_vision, regeneration), so the agent knows exactly what the tool does. It does not differentiate itself from siblings such as clear_effects or give_item, leaving that distinction 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 Guidelines2/5

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

The phrase 'online player' implies the precondition that the target must be connected, but there is no explicit when-to-use guidance, no statement of failure when the player is offline, and no pointer to alternatives like clear_effects for reversal.

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