Skip to main content
Glama

server_create_file

Create new files on Minecraft servers by specifying server ID, directory path, and filename to manage server configurations and resources.

Instructions

Create a new file on a Minecraft server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
parentYesParent directory path
nameYesNew file name

Implementation Reference

  • The 'server_create_file' tool is registered and implemented in src/tools/server-files.ts using server.tool. It uses the client.put method to create a new file by sending the parent directory, filename, and setting directory: false.
    server.tool(
      "server_create_file",
      "Create a new file on a Minecraft server",
      {
        server_id: z.string().describe("Server ID or UUID"),
        parent: z.string().describe("Parent directory path"),
        name: z.string().describe("New file name"),
      },
      async ({ server_id, parent, name }) => {
        try {
          const data = await client.put(`/servers/${server_id}/files/create`, {
            parent,
            name,
            directory: false,
          });
          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 for behavioral disclosure. It states the tool creates a file, implying a write operation, but lacks details on permissions required, whether it overwrites existing files, error handling, or side effects. This is inadequate for a mutation tool with zero annotation coverage.

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 no wasted words. It is front-loaded with the core purpose, 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.

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral details (e.g., permissions, overwrite behavior), usage context, and output information, which are critical for an AI agent to invoke it correctly and safely.

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 all parameters (server_id, parent, name). The description does not add any meaning beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('create a new file') and resource ('on a Minecraft server'), which is specific and unambiguous. However, it does not explicitly differentiate from sibling tools like 'server_create_directory' or 'server_update_file', which would require mentioning it creates files (not directories) and is for new files (not updates).

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 does not mention prerequisites (e.g., server must be running), exclusions (e.g., cannot overwrite existing files), or direct siblings like 'server_create_directory' for directories or 'server_update_file' for modifying files, 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