Skip to main content
Glama

server_update_backup_config

Modify backup settings for Minecraft servers by adjusting retention limits, compression, pre/post commands, and directory exclusions.

Instructions

Update backup configuration for a Minecraft server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
backup_nameNoBackup configuration name
max_backupsNoMaximum number of backups to keep
compressNoCompress backups
shutdownNoShut down server before backup
beforeNoCommand to run before backup
afterNoCommand to run after backup
excluded_dirsNoDirectories to exclude from backup

Implementation Reference

  • The tool "server_update_backup_config" is defined and implemented within the `registerServerBackupTools` function in `src/tools/server-backups.ts`. The handler uses the `CraftyClient` to send a PATCH request to the server's backup configuration endpoint.
    server.tool(
      "server_update_backup_config",
      "Update backup configuration for a Minecraft server",
      {
        server_id: z.string().describe("Server ID or UUID"),
        backup_name: z.string().min(3).optional().describe("Backup configuration name"),
        max_backups: z.number().optional().describe("Maximum number of backups to keep"),
        compress: z.boolean().optional().describe("Compress backups"),
        shutdown: z.boolean().optional().describe("Shut down server before backup"),
        before: z.string().optional().describe("Command to run before backup"),
        after: z.string().optional().describe("Command to run after backup"),
        excluded_dirs: z.array(z.string()).optional().describe("Directories to exclude from backup"),
      },
      async ({ server_id, ...updates }) => {
        try {
          const data = await client.patch(`/servers/${server_id}/backups/config`, 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. 'Update' implies a mutation operation, but the description doesn't mention required permissions, whether changes are immediate or require server restart, what happens to existing backup configurations, or error conditions. This leaves significant behavioral gaps for a configuration mutation 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?

The description is a single, focused sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information.

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 configuration mutation tool with 8 parameters and no annotations or output schema, the description is insufficient. It doesn't explain what happens when the tool executes, what the response looks like, error conditions, or dependencies. The combination of mutation operation, multiple parameters, and lack of structured metadata requires more descriptive context.

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?

With 100% schema description coverage, all parameters are documented in the schema itself. The description doesn't add any additional parameter semantics beyond what's in the schema descriptions, so it meets the baseline for high schema coverage but doesn't provide extra value.

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 action ('Update') and resource ('backup configuration for a Minecraft server'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'server_update' or 'server_update_config' which might handle other configuration aspects, so it doesn't achieve full sibling differentiation.

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 sibling tools like 'server_get_backup_config' (for reading) and 'server_backup' (for creating backups), there's no indication of when this update tool is appropriate versus those other backup-related operations.

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