Skip to main content
Glama

Create directory on VPS

vps_mkdir
Idempotent

Create a directory on a VPS over SFTP. With recursive (the default) missing parents are created and an existing directory is not an error; with recursive false the parent must exist and an existing directory fails. For webspaces use webspace_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": "vps_mkdir"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
pathYesAbsolute path of the directory to create
recursiveNoCreate parent directories as needed (default true)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/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, so safety is covered. The description adds real behavioral detail beyond that: with recursive (default) missing parents are created and an existing directory is not an error, while recursive false changes both the parent requirement and the failure case. It doesn't cover permission/SFTP-auth failure modes, keeping it short of a 5.

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?

Two sentences, no filler, with the core action and mode semantics front-loaded ahead of the sibling pointer. Every clause carries distinct information.

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 three-parameter, non-destructive filesystem tool with rich annotations and full schema coverage, the description supplies everything needed to call it correctly, including default behavior. Only failure modes like insufficient permissions or connectivity gaps are unaddressed.

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 description coverage is 100%, so the baseline is 3; the description still earns a bump by explaining what recursive actually changes in outcomes (parent creation and error behavior on existing directories) rather than restating 'create parent directories as needed'. The id and path parameters are left to the schema, which is acceptable given full coverage.

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 states a specific verb and resource ('Create a directory on a VPS') plus the transport ('over SFTP'), which is more specific than the title alone. It explicitly contrasts itself with the sibling webspace_mkdir, so an agent can pick the right tool without opening either schema.

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

Usage Guidelines5/5

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

It names the alternative tool and the exact condition that routes to it ('For webspaces use webspace_mkdir'). Combined with the recursive on/off semantics, an agent knows both which tool to select and which mode to use.

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.