Skip to main content
Glama

pardon_player

Remove a player ban to restore server access. This tool allows administrators to lift restrictions and reinstate banned users in Minecraft servers.

Instructions

Remove a ban from a player.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playerYesPlayer name

Implementation Reference

  • The 'pardon_player' tool implementation, which registers the tool and sends the 'pardon' command to the server via the RCON manager.
    server.tool(
      "pardon_player",
      "Remove a ban from a player.",
      {
        player: z.string().describe("Player name"),
      },
      async ({ player }) => {
        try {
          const response = await manager.rcon.send(`pardon ${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?

No annotations provided, so description carries full burden. States the mutation (removing a ban) but omits behavioral details like error conditions (what happens if player isn't banned?), reversibility, or timing. Adequate but minimal for a simple single-parameter tool.

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?

Extremely concise at 6 words. Front-loaded with action verb, zero redundancy or filler. Every word earns its place.

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

Completeness4/5

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

Appropriate for low complexity (1 param, 100% schema coverage, no output schema). Description sufficiently captures the core operation, though it could strengthen completeness by explicitly noting the inverse relationship with ban_player or error handling for non-banned players.

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: 'Player name'), establishing baseline 3. Description implies the player parameter is the subject of the pardon action, but doesn't add syntax, format requirements, 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.

Purpose5/5

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

Clear specific verb (Remove) + resource (ban) + target (player). Clearly distinguishes from sibling 'ban_player' (adds ban) and 'kick_player' (temporary removal) via the specific term 'pardon'/'ban'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides implied usage through the action verb, but lacks explicit guidance on when to use versus alternatives (e.g., 'Use when you need to unban a player previously banned by ban_player') or prerequisites (e.g., player must currently be banned).

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