Skip to main content
Glama

server_update

Update Minecraft server configuration settings including name, ports, auto-start, crash detection, and stop commands.

Instructions

Update a Minecraft server's configuration (name, ports, auto-start, crash detection, stop command, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
updatesYesConfiguration fields to update

Implementation Reference

  • The "server_update" tool is registered and implemented directly in src/tools/servers.ts. The handler uses the CraftyClient to perform a PATCH request to /servers/${server_id} with the provided updates.
    server.tool(
      "server_update",
      "Update a Minecraft server's configuration (name, ports, auto-start, crash detection, stop command, etc.)",
      {
        server_id: z.string().describe("Server ID or UUID"),
        updates: z.record(z.string(), z.unknown()).describe("Configuration fields to update"),
      },
      async ({ server_id, updates }) => {
        try {
          const data = await client.patch(`/servers/${server_id}`, updates);
          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 'Update' implies a mutation operation, the description doesn't address important behavioral aspects: whether this requires specific permissions, if changes are reversible, what happens to unspecified configuration fields, error handling, or response format. The 'etc.' suggests incomplete coverage of updatable fields.

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 a single, efficient sentence that gets straight to the point. The parenthetical examples provide helpful context without unnecessary elaboration. However, the 'etc.' at the end feels like a shortcut that could be more precise.

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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what the tool returns, error conditions, permission requirements, or side effects. Given the complexity of server configuration updates and the lack of structured safety information, more behavioral context is needed for safe and effective use.

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 mentions configuration fields like 'name, ports, auto-start' which gives context for what might go in the 'updates' object, but doesn't provide format details or constraints beyond what the schema indicates.

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 states the verb ('Update') and resource ('Minecraft server's configuration'), and provides specific examples of what can be updated (name, ports, auto-start, etc.). However, it doesn't explicitly distinguish this tool from sibling tools like 'crafty_update_config' or 'server_update_backup_config', which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools like 'server_update_backup_config' or 'server_update_file' that might handle specific configuration aspects, there's no indication of scope boundaries or prerequisites for using this general update tool.

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