Skip to main content
Glama

server_decompress_file

Decompress archive files on a Minecraft server to extract game files, mods, or configurations using the crafty-mcp server tool.

Instructions

Decompress/unzip an archive file on a Minecraft server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
folderYesRelative path to the archive file to decompress

Implementation Reference

  • The tool "server_decompress_file" is registered and handled within the `registerServerFileTools` function in `src/tools/server-files.ts`. It takes `server_id` and `folder` (path to archive) as inputs and sends a POST request to `/servers/${server_id}/files/zip`.
    server.tool(
      "server_decompress_file",
      "Decompress/unzip an archive file on a Minecraft server",
      {
        server_id: z.string().describe("Server ID or UUID"),
        folder: z.string().describe("Relative path to the archive file to decompress"),
      },
      async ({ server_id, folder }) => {
        try {
          const data = await client.post(`/servers/${server_id}/files/zip`, { folder });
          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. It states the operation but doesn't cover critical aspects like required permissions, whether it overwrites existing files, supported archive formats, error conditions, or output behavior. This is inadequate for a 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, efficient sentence with zero wasted words. It's front-loaded with the core action and target, making it immediately understandable.

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 file mutation tool with no annotations and no output schema, the description is insufficient. It lacks information about behavioral traits, error handling, supported formats, and what happens post-decompression. The high schema coverage doesn't compensate for these gaps in operational 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?

Schema description coverage is 100%, so the schema already documents both parameters adequately. The description doesn't add any parameter-specific details beyond what's in the schema (e.g., archive format requirements, path conventions), meeting the baseline for high schema coverage.

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 ('decompress/unzip') and target ('an archive file on a Minecraft server'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like server_create_file or server_update_file, which handle different file operations.

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. The description doesn't mention prerequisites (e.g., file must exist), exclusions, or related tools for compression operations, leaving usage context unclear.

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