Skip to main content
Glama

whitelist_manage

Manage Minecraft server whitelist to control player access. Add or remove players, toggle whitelist status, and list current whitelisted users for server security.

Instructions

Manage the server whitelist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhitelist action
playerNoPlayer name (required for add/remove)

Implementation Reference

  • The tool 'whitelist_manage' is registered and implemented in src/tools/player-tools.ts. It uses the server.tool method to define the schema and the async handler to process whitelist actions via RCON commands.
    server.tool(
      "whitelist_manage",
      "Manage the server whitelist.",
      {
        action: z
          .enum(["add", "remove", "list", "on", "off", "reload"])
          .describe("Whitelist action"),
        player: z
          .string()
          .optional()
          .describe("Player name (required for add/remove)"),
      },
      async ({ action, player }) => {
        let cmd: string;
        if (action === "add" || action === "remove") {
          if (!player) {
            return {
              content: [
                {
                  type: "text",
                  text: `Player name is required for whitelist ${action}.`,
                },
              ],
              isError: true,
            };
          }
          cmd = `whitelist ${action} ${player}`;
        } else {
          cmd = `whitelist ${action}`;
        }
    
        try {
          const response = await manager.rcon.send(cmd);
          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?

With no annotations provided, the description carries the full burden of behavioral disclosure but adds none. It doesn't explain that 'whitelist on' restricts server access to only listed players, what 'reload' does, whether changes are immediate or require restart, or potential side effects of disabling the whitelist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While brief (4 words), the description is under-informative rather than efficiently concise. It is front-loaded but sacrifices critical context necessary for a security-sensitive operation. The single sentence doesn't earn its place by providing actionable guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this controls server access (security-critical) and lacks annotations or output schema, the description should explain the whitelist mechanism, return values, and side effects. It fails to explain what distinguishes this from other player management tools in the extensive sibling list.

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% (both parameters documented), establishing a baseline of 3. The description adds no additional semantics about the action enum values (add/remove/list/on/off/reload) or player parameter format beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Manage the server whitelist' essentially restates the tool name with minimal expansion. While it identifies the resource (whitelist), it uses the vague verb 'manage' and fails to distinguish this from sibling player-management tools like ban_player or op_player, or clarify that whitelist restricts access to only listed players.

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?

Description provides no guidance on when to use this tool versus alternatives (e.g., ban_player for banning vs whitelisting for access control), when specific actions are appropriate (on/off vs add/remove), or prerequisites. The agent cannot determine from the description alone whether to use this for player moderation or server security.

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