Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Directory

create_directory

Creates a directory and any missing parent directories, with configurable octal permissions and optional sudo, for setting up required paths during system or security workflows.

Instructions

Create a directory (and parents). mode is octal like '755'.

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
modeNo755
pathYes
sudoNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one meaningful behavior beyond the schema — that parent directories are created — plus the octal format for mode. However, it omits whether existing directories cause an error, what sudo changes in privilege terms, and what the typical failure modes are for a mutation tool.

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?

Two short sentences with no filler, and the core action plus the parent-creation scope are front-loaded. The mode note follows logically. Nothing wasteful, though it is arguably too terse for a 3-parameter 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?

An output schema exists, so return values need no explanation, and the core action is covered. Still, for an unannotated mutation tool with three parameters, the description leaves the sudo parameter and the overwrite/idempotency behavior undocumented, which an agent may need before calling it.

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 0% across three parameters, so the description must compensate. It clarifies that mode is an octal string such as '755', which the bare schema does not convey, but it leaves the sudo flag entirely unexplained and says nothing about path formatting (absolute vs relative).

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?

The description gives a specific verb and resource ("Create a directory") and adds the parent-creation scope, which distinguishes it from sibling operations like delete_path or list_directory. It stops short of naming a sibling explicitly, so it lands at a clear 4 rather than 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?

There is no guidance on when to prefer this tool, no mention of what happens if the path already exists, and no prerequisites or exclusions. The only implied context is filesystem creation, which an agent could already infer from the name.

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

Deploy Server

Other Tools