Skip to main content
Glama

configure_mcp

Update Minecraft server configuration settings including server directory, JAR path, RCON settings, Java path, and JVM arguments to customize server operation.

Instructions

Update the MCP server configuration (server directory, JAR path, RCON settings, Java path, JVM args).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_dirNoPath to the Minecraft server directory
server_jarNoServer JAR filename or path
java_pathNoJava executable path
jvm_argsNoJVM arguments array
rcon_hostNoRCON host
rcon_portNoRCON port
rcon_passwordNoRCON password
backup_dirNoBackup directory path

Implementation Reference

  • The `configure_mcp` tool is defined in `src/tools/server-tools.ts` using `server.tool`. It accepts various configuration parameters, updates the server manager's configuration via `manager.updateConfig`, and returns the updated configuration.
    // --- Configure Server ---
    server.tool(
      "configure_mcp",
      "Update the MCP server configuration (server directory, JAR path, RCON settings, Java path, JVM args).",
      {
        server_dir: z.string().optional().describe("Path to the Minecraft server directory"),
        server_jar: z.string().optional().describe("Server JAR filename or path"),
        java_path: z.string().optional().describe("Java executable path"),
        jvm_args: z.array(z.string()).optional().describe("JVM arguments array"),
        rcon_host: z.string().optional().describe("RCON host"),
        rcon_port: z.number().optional().describe("RCON port"),
        rcon_password: z.string().optional().describe("RCON password"),
        backup_dir: z.string().optional().describe("Backup directory path"),
      },
      async (params) => {
        const updates: Record<string, unknown> = {};
        if (params.server_dir) updates.serverDir = params.server_dir;
        if (params.server_jar) updates.serverJar = params.server_jar;
        if (params.java_path) updates.javaPath = params.java_path;
        if (params.jvm_args) updates.jvmArgs = params.jvm_args;
        if (params.rcon_host) updates.rconHost = params.rcon_host;
        if (params.rcon_port) updates.rconPort = params.rcon_port;
        if (params.rcon_password) updates.rconPassword = params.rcon_password;
        if (params.backup_dir) updates.backupDir = params.backup_dir;
    
        manager.updateConfig(updates);
        const config = manager.getConfig();
        return {
          content: [
            {
              type: "text",
              text: `Configuration updated:\n${JSON.stringify(config, null, 2)}`,
            },
          ],
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure but fails to specify whether changes are immediate or require restart, whether paths are validated, if settings persist across sessions, or what errors might occur. It only states what fields can be updated without operational context.

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?

The description is efficiently structured as a single sentence with a clear verb front-load and parenthetical enumeration. Every word contributes meaning, though the brevity is insufficient given the lack of annotations and output schema.

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?

Given 8 parameters, zero annotations, and no output schema, the description is incomplete. It fails to mention the backup_dir parameter, describe return behavior, or explain configuration validation. For a tool modifying executable paths and connection settings, this lack of operational detail leaves critical gaps.

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%, establishing a baseline of 3. The description lists most parameters (omitting 'backup_dir') and groups related RCON fields, but adds minimal semantic depth beyond the schema's own descriptions. It does not explain parameter relationships (e.g., that server_jar should exist within server_dir).

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?

The description clearly identifies the action ('Update') and target ('MCP server configuration'), listing specific configurable aspects including server directory, JAR path, RCON settings, Java path, and JVM args. However, it does not explicitly distinguish this infrastructure-configuration tool from siblings like 'set_server_property' or 'set_server_properties_bulk' which likely configure in-game Minecraft properties rather than file paths and executables.

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 explicit guidance is provided on when to use this tool versus alternatives, nor are prerequisites stated (e.g., whether the server must be stopped). The description implies usage through the parenthetical list but lacks 'when to use' or 'when not to use' instructions.

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