Skip to main content
Glama

op_player

Grant operator privileges to a player on a Minecraft Java Edition server, enabling administrative control for server management and moderation.

Instructions

Grant operator status to a player.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playerYesPlayer name

Implementation Reference

  • Implementation of the 'op_player' tool handler in 'src/tools/player-tools.ts'. It takes a player name as input and sends an 'op' command via RCON.
    server.tool(
      "op_player",
      "Grant operator status to a player.",
      {
        player: z.string().describe("Player name"),
      },
      async ({ player }) => {
        try {
          const response = await manager.rcon.send(`op ${player}`);
          return { content: [{ type: "text", text: response }] };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Failed: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden. 'Grant' implies a write/mutation operation and privilege escalation, but lacks details on what operator status entails (permissions scope), persistence, or safety implications.

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?

Single sentence with no redundant words efficiently communicates the core action. However, extreme brevity sacrifices necessary behavioral context for a privileged operation.

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 for a single-parameter tool with complete schema coverage, but minimal for a privileged operation. Does not explain operator privileges, prerequisites, or relationship to deop_player despite being a significant permission change.

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 has 100% description coverage ('Player name'), so the schema documents the parameter fully. The description adds no semantic details beyond the schema, warranting the baseline score for high-coverage schemas.

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?

Clear verb 'Grant' and resource 'operator status' with clear target 'player'. However, does not explicitly differentiate from sibling tool deop_player or explain when to prefer this over other moderation tools like 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., existing player), or side effects. Only states the action without context.

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