Skip to main content
Glama

kick_player

Remove a player from a Minecraft server with an optional reason, enabling administrator-level moderation and player management through the MCP protocol.

Instructions

Kick a player from the server with an optional reason.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playerYesPlayer name
reasonNoKick reason message

Implementation Reference

  • The kick_player tool handler registers the MCP tool, defines its schema using Zod, and executes the kick command via RCON.
    server.tool(
      "kick_player",
      "Kick a player from the server with an optional reason.",
      {
        player: z.string().describe("Player name"),
        reason: z.string().optional().describe("Kick reason message"),
      },
      async ({ player, reason }) => {
        const cmd = reason ? `kick ${player} ${reason}` : `kick ${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?

No annotations provided, so description carries full burden. States the action but fails to disclose if the player can immediately rejoin, if the action is logged, success/failure indicators, 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.

Conciseness5/5

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

Single sentence that is appropriately front-loaded. Every word earns its place—no redundancy or unnecessary elaboration while conveying the core 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 simple 2-parameter tool with full schema coverage. However, given no output schema and no annotations, the description could improve completeness by mentioning success behavior or that the target player must be online.

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% ('Player name', 'Kick reason message'), establishing baseline 3. Description adds confirmation that 'reason' is optional, but adds no syntax details, format constraints, or examples beyond what the schema provides.

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 ('Kick') and resource ('player') with scope ('from the server'). However, it does not explicitly differentiate from the sibling 'ban_player' tool, which is a critical distinction for moderation actions.

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?

Mentions the 'reason' parameter is optional but provides no guidance on when to use kick versus ban_player, or prerequisites like player being online. No exclusion criteria or alternatives named.

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