Skip to main content
Glama

create_directory

Create new directories or ensure existing ones using absolute paths for reliable file system organization within Desktop Commander MCP.

Instructions

                    Create a new directory or ensure a directory exists.
                    
                    Can create multiple nested directories in one operation.
                    Only works within allowed directories.
                    
                    IMPORTANT: Always use absolute paths for reliability. Paths are automatically normalized regardless of slash direction. Relative paths may fail as they depend on the current working directory. Tilde paths (~/...) might not work in all contexts. Unless the user explicitly asks for relative paths, use absolute paths.
                    This command can be referenced as "DC: ..." or "use Desktop Commander to ..." in your instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Implementation Reference

  • Handler function that processes the create_directory tool call: validates input with schema, calls the createDirectory helper, and returns success/error response.
    /**
     * Handle create_directory command
     */
    export async function handleCreateDirectory(args: unknown): Promise<ServerResult> {
        try {
            const parsed = CreateDirectoryArgsSchema.parse(args);
            await createDirectory(parsed.path);
            return {
                content: [{ type: "text", text: `Successfully created directory ${parsed.path}` }],
            };
        } catch (error) {
            const errorMessage = error instanceof Error ? error.message : String(error);
            return createErrorResponse(errorMessage);
        }
    }
  • Zod schema for validating create_directory tool arguments (requires 'path' string).
    export const CreateDirectoryArgsSchema = z.object({
      path: z.string(),
    });
  • Core implementation: validates the path and creates directory recursively using fs.mkdir.
    export async function createDirectory(dirPath: string): Promise<void> {
        const validPath = await validatePath(dirPath);
        await fs.mkdir(validPath, { recursive: true });
    }
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate it's not read-only and not destructive, but the description adds valuable context: it can create multiple nested directories, works only within allowed directories, and details path handling (absolute vs. relative, normalization, tilde limitations). This goes beyond annotations, though it doesn't cover rate limits or auth needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with core functionality, followed by important usage notes. Most sentences earn their place, though the final sentence about command referencing is slightly extraneous but not wasteful.

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

Completeness4/5

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

Given the tool's moderate complexity (creation with nesting), no output schema, and annotations covering basic safety, the description is largely complete. It explains behavior, constraints, and parameters well, but could note response format or error conditions for full completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage for the single 'path' parameter, the description compensates by explaining path semantics: must be absolute for reliability, automatically normalized, and relative/tilde paths may fail. This adds crucial meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific verb ('create' or 'ensure exists') and resource ('directory'), distinguishing it from sibling tools like list_directory, move_file, or write_file. It precisely defines the operation's scope and capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance is provided on when to use this tool: for creating directories, ensuring they exist, or creating nested directories. It also specifies when not to use it (e.g., for file operations, which are handled by siblings like write_file or move_file), and emphasizes absolute paths for reliability.

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/wonderwhy-er/ClaudeComputerCommander'

If you have feedback or need assistance with the MCP directory API, please join our Discord server