Skip to main content
Glama

server_create_directory

Create a new directory on a Minecraft server by specifying server ID, parent path, and directory name to organize server files.

Instructions

Create a new directory on a Minecraft server

Input Schema

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

Implementation Reference

  • The handler function for the server_create_directory tool, which makes a PUT request to the server API to create a directory.
    async ({ server_id, parent, name }) => {
      try {
        const data = await client.put(`/servers/${server_id}/files/create`, {
          parent,
          name,
          directory: true,
        });
        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 };
      }
  • The registration block for the server_create_directory tool using the MCP server instance.
    server.tool(
      "server_create_directory",
      "Create a new directory 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 directory name"),
      },
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. While 'Create' implies a write/mutation operation, the description doesn't address important behavioral aspects like required permissions, whether the operation is idempotent, what happens if the directory already exists, or any rate limits. It provides only the basic action without operational context.

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 states the core functionality without unnecessary words. It's appropriately sized for a straightforward tool and front-loads the essential information immediately.

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 insufficiently complete. It doesn't address what the tool returns, error conditions, or important behavioral considerations like whether parent directories must exist or path format requirements. The combination of mutation operation + no structured metadata requires more descriptive 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 all three parameters (server_id, parent, name) with their types and basic descriptions. The tool description adds no additional parameter information beyond what's in the schema, meeting the baseline expectation but not providing extra value.

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 directory') and target resource ('on a Minecraft server'), making the purpose immediately understandable. It doesn't specifically differentiate from sibling tools like 'server_create_file' or 'server_create', but the verb+resource combination is sufficiently specific for basic understanding.

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 about when to use this tool versus alternatives like 'server_create_file' or general 'server_create'. The description doesn't mention prerequisites, constraints, or appropriate contexts for directory creation versus other server operations.

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