Skip to main content
Glama

create_directory

Create new directories in your notes system to organize content, including nested folders in a single operation.

Instructions

Create a new directory in your notes. Can create nested directories in one operation. Path should be relative to your notes directory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesDirectory path to create, relative to notes directory

Implementation Reference

  • The core handler function for the 'create_directory' tool. It validates the input path, ensures it's within the notes directory for security, creates the directory using fs.mkdir with recursive: true, and returns a success or error message.
    export async function handleCreateDirectory(notesPath: string, args: CreateDirectoryArgs): Promise<ToolCallResult> {
      try {
        // Validate path parameter
        if (!args.path) {
          throw new Error("'path' parameter is required");
        }
        
        const dirPath = path.join(notesPath, args.path);
        
        // Ensure the path is within allowed directory
        if (!dirPath.startsWith(notesPath)) {
          throw new Error("Access denied - path outside notes directory");
        }
        
        try {
          await fs.mkdir(dirPath, { recursive: true });
          return {
            content: [{ 
              type: "text", 
              text: `Successfully created directory: ${args.path}` 
            }]
          };
        } catch (error) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          throw new Error(`Error creating directory: ${errorMessage}`);
        }
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [{ type: "text", text: `Error creating directory: ${errorMessage}` }],
          isError: true
        };
      }
    }
  • The tool definition including name, description, and input schema for 'create_directory' returned by getFilesystemToolDefinitions().
    {
      name: "create_directory",
      description: "Create a new directory in your notes. " +
        "Can create nested directories in one operation. " +
        "Path should be relative to your notes directory.",
      inputSchema: {
        type: "object",
        properties: {
          path: { 
            type: "string",
            description: "Directory path to create, relative to notes directory" 
          }
        },
        required: ["path"]
      },
    }
  • Type definition for the arguments accepted by the create_directory handler.
    interface CreateDirectoryArgs {
      path: string;
    }
  • Registration in the main tool dispatcher switch statement in handleToolCall, which routes calls to the filesystem handler.
    case "create_directory":
      return await handleCreateDirectory(notesPath, args);
  • The filesystem tools (including create_directory) are spread into the main getToolDefinitions() array for overall tool registration.
    ...filesystemTools
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds useful context beyond the input schema by mentioning the ability to 'create nested directories in one operation,' which clarifies a behavioral trait (batch creation). However, it lacks details on permissions, error handling (e.g., if the directory already exists), or what happens upon success, leaving gaps in transparency 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 appropriately sized and front-loaded, consisting of two concise sentences that directly convey the tool's function and key details (nested creation and path relativity). Every sentence earns its place without redundancy, making it efficient and well-structured for quick comprehension.

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

Completeness3/5

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

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is moderately complete. It covers the basic purpose and usage context but lacks information on behavioral outcomes (e.g., what is returned or any side effects). For a create operation, this leaves room for improvement in providing a fuller picture to the agent.

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?

The input schema has 100% description coverage, with the 'path' parameter fully documented in the schema itself. The description adds minimal value by reiterating that the path is 'relative to notes directory,' which is already stated in the schema description. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description does not significantly enhance parameter understanding.

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 tool's purpose with a specific verb ('Create') and resource ('new directory in your notes'), distinguishing it from sibling tools like list_directory, search_files, or write_note. It specifies the scope (notes directory) and capability (nested directories in one operation), making the purpose unambiguous and distinct.

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

Usage Guidelines4/5

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

The description provides clear context on when to use this tool by stating it creates directories 'in your notes' and that the path is 'relative to your notes directory,' which implicitly suggests usage for organizing notes. However, it does not explicitly mention when not to use it or name alternatives (e.g., using write_note for files instead of directories), so it falls short of a perfect score.

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/mikeysrecipes/mcp-notes'

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