Skip to main content
Glama

Create directory on webspace

webspace_mkdir
Idempotent

Create a directory inside a webspace as its unprivileged site user, jailed to the home directory. With recursive (the default) missing parents are created and an existing directory is not an error; with recursive false the parent must exist. For a VPS use vps_mkdir.

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": {
      "id": "<id>",
      "path": "<path>"
    },
    "name": "webspace_mkdir"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
pathYesPath relative to the webspace's home directory, or absolute under /home/<user>/. The web root is public_html.
recursiveNoCreate missing parent directories (default true)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description earns extra credit by explaining WHY it is idempotent ('an existing directory is not an error') and by disclosing the privilege model (unprivileged site user, jailed to home). It stops short of stating what permissions the new directory gets or what an out-of-home absolute path does.

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?

Three compact clauses: what it does, how the recursive flag changes behavior, and where the VPS alternative lives. Front-loaded with the action and zero filler, so every sentence earns its place.

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 mutation tool with no output schema, the definition covers safety profile via annotations, privilege context, path scoping and both recursive modes. The only gap is the return value (e.g., whether the created path or a confirmation comes back), which an agent would otherwise infer for a successful create.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real semantics beyond the schema: the default of recursive and the divergent failure modes (parents auto-created vs parent must already exist). That directly informs flag choice rather than restating the field text.

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?

States a specific verb and resource (create a directory inside a webspace) plus the execution context (runs as the unprivileged site user, jailed to the home directory), and names the sibling it is not (vps_mkdir). An agent can distinguish it from vps_mkdir and webspace_create without opening any schema.

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?

Gives explicit routing guidance with the alternative: 'For a VPS use vps_mkdir.' It also frames the two calling modes via the recursive flag. What it does not cover is when to choose this over other webspace path tools (write_file, rename), but the platform split is clearly handled.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.