Skip to main content
Glama

execute_commands

Execute multiple Minecraft commands sequentially via RCON to perform batch operations such as building structures or setting up game scenarios.

Instructions

Execute multiple Minecraft commands sequentially via RCON. Useful for batch operations like building structures or setting up game scenarios.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandsYesArray of commands to execute in order (without leading '/')

Implementation Reference

  • The `execute_commands` tool handler implementation, which uses `manager.rcon.sendMultiple` to execute a list of commands sequentially.
    server.tool(
      "execute_commands",
      "Execute multiple Minecraft commands sequentially via RCON. Useful for batch operations like building structures or setting up game scenarios.",
      {
        commands: z
          .array(z.string())
          .describe("Array of commands to execute in order (without leading '/')"),
      },
      async ({ commands }) => {
        try {
          const results = await manager.rcon.sendMultiple(commands);
          const lines = results.map(
            (r) => `> ${r.command}\n  ${r.response || "(no response)"}`
          );
          return { content: [{ type: "text", text: lines.join("\n\n") }] };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to execute commands: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses transport mechanism (RCON) and execution order (sequential) which are critical behavioral traits. However, given no annotations, it omits important safety context such as destructive potential, error handling (what happens if command N fails), or atomicity guarantees.

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?

Two well-constructed sentences with zero waste: first defines the action, second provides usage context. Front-loaded with the core mechanism (RCON) and appropriately scoped.

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?

Adequate for a single-parameter tool with complete schema coverage. Mentions key technical context (RCON, sequential execution) and use cases. Minor gap: could clarify return values or error behavior given lack of output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage (baseline 3), adds valuable semantic context by illustrating what the commands array represents ('batch operations like building structures or setting up game scenarios'), helping the agent understand intent beyond raw syntax.

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 ('Execute') + resource ('Minecraft commands') + mechanism ('via RCON'). Distinguishes from sibling 'execute_command' by emphasizing 'multiple' and 'sequentially', though it doesn't explicitly name the singular alternative.

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 positive usage guidance ('Useful for batch operations like building structures or setting up game scenarios') indicating when to use it, but lacks negative guidance (when to use singular execute_command instead) or explicit alternative references.

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