Skip to main content
Glama

make_dir

Create a folder on a remote host over SSH by specifying the host and path; relative paths resolve from the home directory.

Instructions

Create a folder on a host.

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": {
      "host": "<host>",
      "path": "<path>"
    },
    "name": "make_dir"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
pathYesA path on the host; relative paths start at the home directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and supplies almost none of it. It does not say whether parent directories are created recursively, whether existing directories cause an error, what permissions or session state are required, or whether the operation is idempotent — all material for a filesystem mutation.

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 single sentence is front-loaded and free of waste, but at six words it is under-specified rather than appropriately concise. Brevity here comes at the cost of the behavioral and usage information an agent needs.

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?

With no annotations, no output schema, and one of two parameters undocumented, the description should be doing far more work than it does. It leaves open the essentials for a mutation tool: error behavior on existing paths, recursive creation, permission requirements, and how to identify the host.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: path is documented in the schema (including the home-directory-relative rule), but host is undocumented in both places. The description adds nothing beyond the schema — it does not say that host expects a host identifier from list_hosts or how the path relates to the target host's filesystem.

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 folder on a host.' An agent can distinguish this from read_file, write_file, rename, or remove without opening the schema. It stops short of differentiating from related filesystem operations (e.g. whether it creates intermediate directories), which keeps it from a 5.

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?

No guidance on when to use this versus alternatives, nor any preconditions such as needing an open session or a registered host. There is no statement about what happens if the folder already exists, which is the most common decision point for an agent choosing this tool.

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