Skip to main content
Glama
KazKozDev
by KazKozDev

Create Directory

create_directory

Create directories for organizing Markdown files in the Markdown Editor MCP Server. Specify a path to establish folders that structure your document hierarchy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNo
successNo

Implementation Reference

  • Core implementation of the create_directory tool: validates path safety using _validate_path, resolves absolute path, creates directory with os.makedirs (exist_ok=True), returns success dict or error.
    async def create_directory(self, path: str) -> Dict[str, Any]:
        """Create directory"""
        # Validate path safety
        error = self._validate_path(path)
        if error:
            return {"error": error}
    
        try:
            abs_path = self._get_abs_path(path)
            os.makedirs(abs_path, exist_ok=True)
            return {"success": True, "path": path}
        except Exception as e:
            return {"error": str(e)}
  • Registers the create_directory tool in the MCP server's list_tools() handler, defining name, title, description (implied), inputSchema (path: string required), and outputSchema.
    Tool(
        name="create_directory",
        title="Create Directory",
        inputSchema={
            "type": "object",
            "properties": {
                "path": {
                    "type": "string",
                    "examples": ["./new_folder", "./docs/archive"],
                }
            },
            "required": ["path"],
            "additionalProperties": False,
        },
        outputSchema={
            "type": "object",
            "properties": {
                "success": {"type": "boolean"},
                "path": {"type": "string"},
            },
        },
    ),
  • JSON schema definitions for create_directory tool inputs (object with required 'path' string) and outputs (object with 'success' boolean and 'path' string).
    inputSchema={
        "type": "object",
        "properties": {
            "path": {
                "type": "string",
                "examples": ["./new_folder", "./docs/archive"],
            }
        },
        "required": ["path"],
        "additionalProperties": False,
    },
    outputSchema={
        "type": "object",
        "properties": {
            "success": {"type": "boolean"},
            "path": {"type": "string"},
        },
    },
  • Standalone async wrapper function that delegates to the singleton FileOperationsTool instance's create_directory method.
    async def create_directory(path: str):
        return await _instance.create_directory(path)
  • Dispatch logic in MCP call_tool handler: calls the create_directory function and wraps result in CallToolResult with success message.
    elif name == "create_directory":
        res = await create_directory(arguments["path"])
        return CallToolResult(
            content=[TextContent(type="text", text="Directory created")],
            structuredContent=res,
            isError="error" in res,
        )
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KazKozDev/markdown-editor-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server