Skip to main content
Glama

deop_player

Remove operator privileges from a specified player in a Minecraft server to manage administrative access and permissions.

Instructions

Revoke operator status from a player.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playerYesPlayer name

Implementation Reference

  • The "deop_player" tool is registered and handled within this block. It takes a "player" string as input and executes the "deop" RCON command via the ServerManager.
    server.tool(
      "deop_player",
      "Revoke operator status from a player.",
      {
        player: z.string().describe("Player name"),
      },
      async ({ player }) => {
        try {
          const response = await manager.rcon.send(`deop ${player}`);
          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 provided, so description must carry full disclosure burden. It fails to mention idempotency (what happens if player isn't an operator?), persistence (does this last after restart?), offline player handling, or required permissions.

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?

Extremely concise at six words. No redundancy, but arguably too terse given the complete absence of annotations and output schema—appropriate length for the sentence itself, but insufficient information density for the tool's complexity.

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?

Minimal viability for a single-parameter mutation tool. Lacks behavioral context expected when annotations are absent (e.g., success indicators, side effects), though schema coverage compensates for parameter documentation.

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 coverage is 100% with 'player' described as 'Player name'. The description mentions 'a player' in context, adding minimal semantic depth beyond the schema's literal description. Baseline 3 appropriate given high schema coverage.

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 specific action (revoke) and resource (operator status) clearly. However, it does not explicitly differentiate from sibling tool 'op_player' or clarify when to prefer this over 'kick_player' or 'ban_player'.

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?

Provides no guidance on when to use this tool versus alternatives, prerequisites (e.g., verifying current operator status via list_ops), or failure conditions (e.g., targeting a non-existent player).

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