nextcloud-mcp

move_file

Move or rename files and folders in Nextcloud by entering the current path and the new destination. Simplify file organization with relative path inputs for accurate relocation.

Instructions

Move or rename a file or folder in Nextcloud.

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": {
      "fromPath": "<fromPath>",
      "toPath": "<toPath>"
    },
    "name": "move_file"
  }
}

Input Schema

Name	Required	Description	Default
`toPath`	Yes	New destination path relative to user root
`fromPath`	Yes	Current path of the file/folder relative to user root

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 2, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations are absent, so the description must carry the full burden of behavioral disclosure. It mentions 'Move or rename' but does not disclose potential overwrite behavior, permission requirements, or whether the operation is reversible.

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, direct sentence with zero redundant information. It is appropriately front-loaded and concise.

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?

For a simple 2-parameter tool, the description adequately conveys the core purpose and the schema covers parameter details. However, missing usage guidelines and behavioral transparency leave minor gaps, making it minimally complete.

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?

The input schema fully documents both parameters (fromPath and toPath) with descriptions. The tool description adds no additional parameter context, so the baseline score of 3 applies given 100% schema coverage.

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 states exactly what the tool does: 'Move or rename a file or folder in Nextcloud.' It uses a specific verb and resource, and clearly distinguishes from sibling file tools like get_file, upload_file, and create_folder.

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 is provided about when to use this tool, prerequisites, or alternatives. The description simply states the action without any contextual direction, leaving the agent to infer usage.

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