Skip to main content
Glama
eva-wanxin-git

Windows Automation MCP Server

create_directory

Create new directories on Windows systems to organize files and manage storage structure. Specify the path where the directory should be created.

Instructions

创建目录

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes目录路径

Implementation Reference

  • The handler function that creates the directory using fs.mkdir with recursive option and returns success/error response.
    async createDirectory(dirPath) {
      try {
        await fs.mkdir(dirPath, { recursive: true });
        return { success: true, path: dirPath, message: '目录创建成功' };
      } catch (error) {
        return { success: false, error: error.message };
      }
    }
  • Tool definition including name, description, and input schema for the create_directory tool.
    {
      name: 'create_directory',
      description: '创建目录',
      inputSchema: {
        type: 'object',
        properties: {
          path: { type: 'string', description: '目录路径' },
        },
        required: ['path'],
      },
    },
  • Registration in the executeTool switch statement dispatching to the createDirectory handler.
    case 'create_directory':
      return await this.createDirectory(args.path);
  • Inclusion in the canHandle tools array for checking if the tool can be handled.
    const tools = ['read_file', 'write_file', 'list_directory', 'create_directory', 
                   'delete_file', 'copy_file', 'move_file', 'search_files'];
Behavior1/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. '创建目录' only states the action without any information about permissions required, whether it overwrites existing directories, error conditions (e.g., invalid paths), side effects, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is inadequate.

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

Conciseness3/5

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

The description is extremely concise ('创建目录'), which could be efficient if it were informative. However, it's under-specified rather than appropriately concise—it lacks necessary details for a mutation tool. While front-loaded, it doesn't earn its place by providing sufficient context.

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?

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It doesn't explain what the tool returns, error handling, or behavioral traits. While the parameter is covered by the schema, the overall context for safe and correct usage is missing, making it inadequate for an agent to invoke this tool reliably.

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 description adds no parameter semantics beyond what the input schema provides. However, schema description coverage is 100% (the 'path' parameter is documented in the schema as '目录路径' or 'directory path'), so the baseline score is 3. The description doesn't compensate or add value, but the schema adequately covers the single parameter.

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

Purpose2/5

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

The description '创建目录' (Create directory) is a tautology that essentially restates the tool name 'create_directory' in Chinese. While it does specify the verb ('create') and resource ('directory'), it doesn't distinguish this tool from any potential siblings or provide any additional context about what kind of directory creation this performs (e.g., local filesystem, remote, with specific permissions).

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

Usage Guidelines1/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. Given the sibling tools include file operations like 'copy_file', 'delete_file', 'move_file', and 'list_directory', there's no indication of whether this is for creating directories in a specific context (e.g., browser, system) or any prerequisites. It's completely missing usage context.

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/eva-wanxin-git/windows-automation-mcp'

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