Unrestricted Development MCP Server

fs_create_directory

Create a new directory with option to automatically create parent directories.

Instructions

Create a new directory. Can create parent directories if they don't exist.

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": "fs_create_directory"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute or relative path to the directory to create
`recursive`	No	Create parent directories if they don't exist

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2025

TDQS

A3.6/5.0

Behavior3/5

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

Without annotations, the description carries the full behavioral disclosure burden. It reveals that the tool can create parent directories if they don't exist, adding value beyond the schema. However, it omits details on error behavior (e.g., if directory already exists) or permission requirements.

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?

The description is a single, front-loaded sentence with no wasted words. It efficiently conveys the core action and key nuance (parent directory creation), earning 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?

Given the low complexity (2 params, no output schema), the description is fairly complete. It covers the main functionality and recursive behavior. However, it lacks return value info and error handling, but these are somewhat acceptable for a simple creation tool.

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 coverage is 100%, so baseline is 3. The description adds minimal extra meaning by mentioning parent directory creation, which is already covered by the recursive parameter default. No further param semantics are provided.

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 clearly states the action ('Create a new directory') and the resource, distinguishing it from sibling tools like fs_delete_directory or fs_list_directory. It also adds the specific capability to create parent directories, which differentiates it further.

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 explicit guidance is provided on when to use this tool versus alternatives, such as creating individual directories without parents or handling existing directory errors. The description implies usage context but lacks exclusion criteria or alternative suggestions.

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