ryns-code-mcp

Overview Schema Source Related Servers Discussions Admin

Create Directory

create_directory

Creates a directory recursively on a Linux machine, including missing parent paths, so AI assistants can prepare file locations before writing or processing files.

Instructions

Create a directory recursively.

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

Name	Required	Description	Default
`path`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Nov 3, 2026

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, yet it discloses almost nothing: idempotency (error vs. success when the directory already exists), whether intermediate parents are truly created, permission requirements, and failure modes are all unstated. "Recursively" is the only behavioral hint and remains ambiguous.

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?

A single front-loaded sentence with no filler, which is structurally good, but the brevity crosses into under-specification rather than economy. Nothing after the verb adds information the caller 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?

Although the tool is simple (one required param, no output schema), it has no annotations to fall back on, so the description should cover path semantics and side effects such as overwrite/idempotency behavior. Those gaps leave an agent unable to predict what a call will do in edge cases.

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?

There is one parameter (path) with 0% schema description coverage and the description never mentions it. It does not say whether the path must be absolute or relative, whether it is rooted in the workspace, or whether trailing separators or existing files at that path are acceptable.

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 directory") that clearly distinguishes it from siblings like list_directory, directory_tree, and move_file. The qualifier "recursively" signals parent creation but is left unexplained, so the scope of the operation is only partly pinned down.

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 instead of write_file (which may auto-create paths) or move_file, and no prerequisites or exclusions. The agent must infer everything about selection and ordering from the name alone.

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