Skip to main content
Glama

Move item

nextcloud_move_item

Move or rename one Nextcloud file or folder by setting source and destination paths, with optional overwrite control to manage conflicts.

Instructions

Move or rename one file or folder.

MOVE /remote.php/dav/files/{user}/{source_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": {
      "source_path": "<source_path>",
      "dest_path": "<dest_path>"
    },
    "name": "nextcloud_move_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
dest_pathYes
overwriteNo
source_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.4

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds only an HTTP verb and a DAV path template, and omits the behavior that matters most: whether an existing destination is replaced or the call fails, and whether a rename preserves the item's identity and shares. With no contradiction, this is a transparency gap rather than an error.

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, with the action stated first and the endpoint second. Nothing is padded, though the raw HTTP path template is developer-facing detail rather than guidance the agent can act on.

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?

There is no output schema and no parameter documentation, so the description is the only source of behavioral detail for a mutation tool, and it omits overwrite semantics, failure conditions, and permission requirements. For a destructive-capable filesystem move this leaves the agent under-informed before invoking it.

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?

Schema description coverage is 0% across three parameters, so the description carries the full burden and largely fails it. The path template hints that source_path is a DAV-style path and 'rename' implies dest_path may be a new name, but the overwrite parameter is never mentioned, leaving its role and default unexplained.

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?

The description uses a specific verb pair ('Move or rename') and a bounded resource ('one file or folder'), which lets an agent separate it from siblings like nextcloud_copy_item or nextcloud_delete_item. It stops short of naming those siblings explicitly, so differentiation is inferable rather than stated.

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?

There is no when-to-use guidance and no mention of the alternative nextcloud_copy_item, which is the most likely confusion point given the sibling list. The description also does not say what happens when the destination already exists, which is the key decision an agent must make before calling.

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