Skip to main content
Glama

server_send_command

Send console commands to a running Minecraft server to manage gameplay, permissions, and server settings directly from the MCP interface.

Instructions

Send a command to a running Minecraft server's console. Examples: 'say Hello everyone!', 'op PlayerName', 'whitelist add Player', 'gamemode creative Player', 'time set day', 'weather clear'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
commandYesCommand to send to the server console (without leading slash)

Implementation Reference

  • The `server_send_command` tool is registered using `server.tool` and contains the handler implementation that makes a POST request to the Crafty server's stdin endpoint.
    server.tool(
      "server_send_command",
      "Send a command to a running Minecraft server's console. Examples: 'say Hello everyone!', 'op PlayerName', 'whitelist add Player', 'gamemode creative Player', 'time set day', 'weather clear'",
      {
        server_id: z.string().describe("Server ID or UUID"),
        command: z.string().describe("Command to send to the server console (without leading slash)"),
      },
      async ({ server_id, command }) => {
        try {
          const data = await client.post(`/servers/${server_id}/stdin`, { command });
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: `Error: ${msg}` }], 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 burden for behavioral disclosure. While it mentions the tool sends commands to a 'running' server (implying the server must be active), it doesn't cover critical aspects like required permissions, whether commands are synchronous/asynchronous, error handling, or rate limits. The examples suggest administrative actions but don't explicitly warn about destructive potential.

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 and well-structured. The first sentence clearly states the purpose, followed by relevant examples that earn their place by illustrating command syntax and common use cases. No wasted words or redundant information.

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?

For a mutation tool with no annotations and no output schema, the description is minimally adequate. It covers the basic purpose and provides helpful examples, but lacks important contextual information about behavioral characteristics, error responses, and operational constraints that would be needed for robust agent usage.

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%, so the schema already documents both parameters adequately. The description adds minimal value beyond the schema - it clarifies that commands should be 'without leading slash' (useful context) and provides examples that illustrate the 'command' parameter's expected format, but doesn't add significant semantic depth.

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?

The description clearly states the specific action ('send a command') and target ('to a running Minecraft server's console'), distinguishing it from sibling tools like server_start or server_get_logs. It provides concrete examples that illustrate the tool's function beyond just the name.

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?

The description implies usage context through the examples (e.g., administrative commands like 'op PlayerName'), but doesn't explicitly state when to use this tool versus alternatives like server_update or server_run_task. No guidance on prerequisites or exclusions is provided.

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/HadiCherkaoui/crafty-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server