Skip to main content
Glama

Create Directory

create_directory

Creates one or more directories, including missing parent paths, so you can set up project folder structures in a single step.

Instructions

Create one or more directories (like mkdir -p).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "create_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRelative or absolute path to the directory.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. The 'mkdir -p' analogy usefully conveys recursion and non-failure when the path already exists, but it says nothing about permissions, what happens if a path component is a file, or whether partial creation is rolled back on error.

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?

A single short sentence with the key behavioral cue (mkdir -p) front-loaded and zero filler. Nothing could be removed without losing meaning.

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?

For a one-parameter, low-risk tool with full schema coverage and an output schema, this is close to complete. Only the unstated failure conditions (path is an existing file, permission errors) keep it short of full marks.

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 coverage is 100%, so the path parameter and its relative/absolute semantics are already documented. The description adds no format detail, and 'one or more directories' is mildly ambiguous since only a single path string is accepted.

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?

States a specific verb and resource ('Create ... directories') and adds the 'mkdir -p' analogy, which pins down recursive creation semantics. It is distinguishable from siblings like write_file or create_project_workspace, though it never names them.

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

Usage Guidelines3/5

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

Usage is only implied: the mkdir -p framing tells an agent this is the native way to make nested directories instead of shelling out via run_command. There is no explicit when-to-use or when-not-to-use guidance, and no mention of its relationship to list_directory or delete_path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.