Skip to main content
Glama

Copy item

nextcloud_copy_item

Copy a file or folder to a new destination in Nextcloud, with optional overwrite. Provide source and destination paths to duplicate items and control replacement.

Instructions

Copy one file or folder.

COPY /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_copy_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 declare readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context beyond that. Critically, it says nothing about the overwrite flag's effect, whether copying a folder is recursive, or what error occurs when the destination exists — the most consequential behaviors for a copy tool.

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?

The two-line format is front-loaded and wastes little space. The raw COPY endpoint line is of marginal value to an agent but is compact and does convey path structure.

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?

For a 3-parameter mutation tool with no output schema and zero schema coverage, the definition is thin. It omits overwrite semantics, recursion behavior for folders, destination-collision handling, and the return shape, leaving key call decisions to guesswork.

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%, so the description carries the full burden, and it mostly fails: only the URL template hints that source_path is relative to the user's files root. The optional 'overwrite' parameter (default false) is never explained, and dest_path semantics (folder vs. full target name) are unstated.

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 states a specific verb and resource ('Copy one file or folder'), which is clear enough to distinguish from siblings like nextcloud_write_file or nextcloud_delete_item. It does not, however, differentiate itself from nextcloud_move_item, the nearest sibling.

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 guidance on when to use copy versus nextcloud_move_item, no prerequisites, and no mention of what happens when the destination already exists. The agent must infer everything from the verb.

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