Skip to main content
Glama

server_backup

Trigger an immediate backup of Minecraft server files to protect against data loss. Specify the server ID to initiate the backup process.

Instructions

Trigger an immediate backup of a Minecraft server's files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID

Implementation Reference

  • The tool handler for "server_backup" (and other actions) is implemented dynamically within a loop in registerServerActionTools, which executes a POST request to the server's action endpoint.
    server.tool(
      name,
      description,
      serverIdSchema,
      async ({ server_id }) => {
        try {
          const data = await client.post(`/servers/${server_id}/action/${action}`);
          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 };
        }
      }
    );
  • Definition of the "server_backup" tool, mapping its name to the action "backup_server".
    { name: "server_backup", action: "backup_server", description: "Trigger an immediate backup of a Minecraft server's files" },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool triggers a backup but doesn't describe what happens during the backup (e.g., server performance impact, whether the server is paused), permissions required, rate limits, or what the response looks like (e.g., success/failure, backup ID). For a mutation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence that front-loads the core action ('trigger an immediate backup') and resource ('Minecraft server's files'). There is zero wasted text, and it's appropriately sized for a tool with one parameter.

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 the complexity (a mutation tool that initiates a backup process), lack of annotations, and no output schema, the description is incomplete. It doesn't explain behavioral aspects like what the backup includes, how long it takes, error conditions, or return values. For a tool that likely has side effects, this leaves critical gaps for an AI agent.

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%, with the single parameter 'server_id' documented as 'Server ID or UUID'. The description doesn't add any meaning beyond this, such as where to find the server_id or format examples. With high schema coverage, the baseline is 3 even without param info in the description.

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 ('trigger an immediate backup') and resource ('Minecraft server's files'), distinguishing it from sibling tools like server_list_backups (which lists backups) and server_restore_backup (which restores from a backup). The verb 'trigger' implies initiation of a process rather than just querying.

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. It doesn't mention prerequisites (e.g., whether the server must be running), exclusions, or comparisons to related tools like server_update_backup_config (which configures backup settings) or server_delete_backup (which removes backups).

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