Skip to main content
Glama

apply_effect

Apply status effects like speed, strength, or invisibility to players in Minecraft servers using administrator controls for gameplay management.

Instructions

Apply a status effect to a player. Examples: speed, strength, regeneration, night_vision, invisibility, resistance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesPlayer selector
effectYesEffect ID (e.g., 'speed', 'night_vision')
durationNoDuration in seconds
amplifierNoAmplifier level (0 = level I)

Implementation Reference

  • The tool 'apply_effect' is registered and implemented in src/tools/player-tools.ts. It executes an RCON 'effect give' command.
    server.tool(
      "apply_effect",
      "Apply a status effect to a player. Examples: speed, strength, regeneration, night_vision, invisibility, resistance.",
      {
        target: z.string().describe("Player selector"),
        effect: z.string().describe("Effect ID (e.g., 'speed', 'night_vision')"),
        duration: z.number().optional().default(30).describe("Duration in seconds"),
        amplifier: z.number().optional().default(0).describe("Amplifier level (0 = level I)"),
      },
      async ({ target, effect, duration, amplifier }) => {
        try {
          const response = await manager.rcon.send(
            `effect give ${target} ${effect} ${duration} ${amplifier}`
          );
          return { content: [{ type: "text", text: response }] };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Failed: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It fails to disclose that this modifies game state, whether it overwrites existing effects or stacks with them, failure modes (e.g., invalid effect ID), or that it requires specific server privileges to execute.

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 sentences with zero waste. The first states the core purpose; the second provides immediately useful examples. Every word earns its place and it is appropriately front-loaded.

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?

Adequate but minimal. With 100% schema coverage and simple parameter types, the tool is usable. However, given no output schema and no annotations, the description should ideally address effect stacking behavior, offline player handling, or success confirmation—leaving clear gaps.

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?

With 100% schema coverage, the baseline is 3. The description adds value by providing five concrete effect examples beyond the schema's two parenthetical examples, helping the agent infer valid effect ID formats and common use cases.

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 uses a specific verb ('Apply') + resource ('status effect') + target ('player'), clearly distinguishing it from siblings like give_item (physical items) or ban_player (moderation). The examples further clarify the specific domain of Minecraft potion/effect mechanics.

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 description provides no guidance on when to use this tool versus alternatives, prerequisites (e.g., requiring OP permissions), or constraints (e.g., target must be online). It merely states what the tool does, not when to select it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tamo2918/Minecraft-Server-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server