Skip to main content
Glama

server_delete_file

Remove files or directories from a Minecraft server to manage storage and clean up unnecessary data. Specify server ID and file paths to delete.

Instructions

Delete one or more files or directories from a Minecraft server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
pathsYesArray of relative file paths to delete

Implementation Reference

  • The server_delete_file tool implementation, which accepts server_id and an array of paths to delete from the Minecraft server. It uses the client to perform a DELETE request.
    server.tool(
      "server_delete_file",
      "Delete one or more files or directories from a Minecraft server",
      {
        server_id: z.string().describe("Server ID or UUID"),
        paths: z.array(z.string()).describe("Array of relative file paths to delete"),
      },
      async ({ server_id, paths }) => {
        try {
          const file_system_objects = paths.map((filename) => ({ filename }));
          const data = await client.delete(`/servers/${server_id}/files`, {
            file_system_objects,
          });
          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 the full burden of behavioral disclosure. It mentions deletion but fails to specify critical details like whether the action is irreversible, requires specific permissions, affects server performance, or has rate limits. This leaves significant gaps in understanding the tool's behavior.

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, direct sentence that efficiently conveys the core action without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured for quick comprehension.

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 destructive tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, error handling, return values, and usage context, failing to provide the completeness needed for safe and effective tool invocation in a complex 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%, so the schema fully documents the parameters. The description adds no additional semantic context beyond implying deletion of 'one or more files or directories', which aligns with the 'paths' array parameter but does not enhance understanding beyond the schema's details.

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 ('Delete') and target ('files or directories from a Minecraft server'), making the purpose evident. However, it does not explicitly differentiate from siblings like 'server_delete' (which likely deletes entire servers) or 'server_delete_backup', leaving room for 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?

The description provides no guidance on when to use this tool versus alternatives such as 'server_delete' or 'server_delete_backup'. It lacks context about prerequisites, permissions, or scenarios where this tool is appropriate, offering minimal usage direction.

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