Skip to main content
Glama

Create folder

nextcloud_create_folder

Creates one folder at a specified Nextcloud path, enabling directory setup for organized file storage and uploads.

Instructions

Create one folder.

MKCOL /remote.php/dav/files/{user}/{path}

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.4

TDQS

B3/5.0
Behavior3/5

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

Annotations already disclose readOnly=false, openWorld=true, and destructive=false. The description adds the WebDAV MKCOL endpoint, but it does not state what happens if the folder already exists, whether parent folders must exist, what permissions are required, or what is returned.

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 lines, front-loaded with the purpose statement and no filler. The raw endpoint is cryptic and unexplained, but the overall structure is efficient.

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?

This is a simple one-parameter create operation, and the annotations cover its safety profile. However, the description is still missing path format and duplicate/parent/permission behavior needed for confident use 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?

The single path parameter has 0% schema description coverage. The URL template hints that path is part of the WebDAV path, but the description does not clarify whether it is absolute or relative, whether it includes the user, whether leading slashes are required, or whether nested paths are supported.

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, "Create", and resource, "one folder", which distinguishes it from siblings such as create_document, create_note, and create_user. It does not explicitly contrast with alternative file-creation or write operations, so it is clear but not fully sibling-routing.

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?

Provides no when-to-use, when-not-to-use, or alternative guidance. The MKCOL endpoint is an implementation detail rather than selection guidance, so the agent must infer when this tool is appropriate.

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