Skip to main content
Glama

ban_player

Ban players from a Minecraft server to enforce rules and maintain a safe gaming environment. Specify player name and optional reason for moderation.

Instructions

Ban a player from the server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playerYesPlayer name
reasonNoBan reason

Implementation Reference

  • The ban_player tool is registered and implemented in src/tools/player-tools.ts using the server.tool method. It takes a player name and an optional reason, then sends a 'ban' command via RCON.
    server.tool(
      "ban_player",
      "Ban a player from the server.",
      {
        player: z.string().describe("Player name"),
        reason: z.string().optional().describe("Ban reason"),
      },
      async ({ player, reason }) => {
        const cmd = reason ? `ban ${player} ${reason}` : `ban ${player}`;
        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 full disclosure burden yet fails to state whether the ban is permanent, whether the player is immediately kicked, that it can be reversed via `pardon_player`, or required permission levels.

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 terse at six words with zero redundancy; however, the brevity crosses into under-specification for a destructive moderation action.

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?

Moderate-complexity moderation tool with permanent consequences but no output schema, no annotations, and no behavioral details; insufficient for safe autonomous operation given the severity of the action.

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 documenting 'Player name' and 'Ban reason'. The description adds no parameter semantics beyond what the schema already provides, warranting the baseline score.

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

Purpose3/5

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

The description states the specific action (ban) and resource (player), but fails to distinguish from sibling tool `kick_player` (temporary removal) or clarify that bans are permanent/reversible only via `pardon_player`, which is critical for correct tool selection.

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?

No guidance provided on when to use this versus `kick_player` for temporary disconnects, or any prerequisites like whether the player must be online. Zero alternative or exclusion criteria mentioned.

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