Skip to main content
Glama

create_folder

Creates a new directory inside the allowed root path, letting AI clients organize cPanel files by making folders at the root or within a parent directory.

Instructions

Create a new directory inside ALLOWED_ROOT.

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": {
      "name": "<name>"
    },
    "name": "create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoParent directory relative path (leave empty for root).
nameYesNew folder name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses one useful constraint, the ALLOWED_ROOT sandbox, but says nothing about what happens when the folder already exists, when the parent path is invalid, or what the tool returns on success or failure.

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?

A single front-loaded sentence with no wasted words. Its brevity is efficient, though it borders on under-specification for a filesystem mutation.

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?

For a simple two-parameter creation tool with a fully described schema and no output schema, the description is minimally adequate. It still leaves error behavior, overwrite semantics, and success response unexplained, which matters for a mutation tool with no annotations.

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 both 'dir' and 'name' are already documented, and the description adds only the ALLOWED_ROOT boundary context. That matches the baseline for a fully documented schema with no additional parameter meaning supplied.

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 a new directory') plus a scope constraint ('inside ALLOWED_ROOT'), so the agent knows exactly what the tool does. It does not need to differentiate from siblings such as write_file or rename_or_move, since none of them create directories, but it also never says so explicitly.

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?

There is no guidance on when to use this versus related file operations, nor any mention of prerequisites such as the parent directory needing to exist or permissions required. The agent must infer all usage conditions from the name alone.

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