Skip to main content
Glama

server_list_backups

Retrieve a list of all Minecraft server backups with timestamps and file sizes to monitor backup history and manage storage.

Instructions

List all backups for a Minecraft server with timestamps and sizes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID

Implementation Reference

  • The server_list_backups tool is defined and implemented within the server.tool() call in registerServerBackupTools. It takes a server_id, calls the client to fetch backups, and returns the formatted response.
    server.tool(
      "server_list_backups",
      "List all backups for a Minecraft server with timestamps and sizes",
      { server_id: z.string().describe("Server ID or UUID") },
      async ({ server_id }) => {
        try {
          const data = await client.get(`/servers/${server_id}/backups`);
          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?

No annotations are provided, so the description carries full burden. It implies a read-only operation by using 'List,' but doesn't disclose behavioral traits such as authentication requirements, rate limits, pagination, error handling, or whether it's a safe operation. For a tool with no annotations, this leaves significant gaps in understanding how it behaves.

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 key information ('List all backups for a Minecraft server') and adds useful details ('with timestamps and sizes'). There is no wasted wording, making it easy to scan and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally complete. It covers the basic purpose but lacks context on usage, behavior, and output format. Without annotations or output schema, more detail on what the list returns (e.g., structure, limitations) would improve completeness for a tool in this environment.

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 parameter 'server_id' fully documented in the schema. The description doesn't add any meaning beyond the schema, as it doesn't explain parameter usage, constraints, or examples. With high schema coverage, the baseline score of 3 is appropriate, but no extra value is provided.

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 ('List all backups') and resource ('for a Minecraft server'), specifying what information is included ('with timestamps and sizes'). It distinguishes from siblings like 'server_get_backup_config' or 'server_restore_backup' by focusing on listing rather than configuration or restoration. However, it doesn't explicitly differentiate from 'server_backup' (which likely creates backups), leaving some ambiguity.

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid server ID), exclusions, or comparisons to related tools like 'server_list' (for servers) or 'server_get_history' (which might include backup history). The description assumes context but offers no explicit usage rules.

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