mcp-pcloud

pcloud_copy_folder

Copies a folder from a source path to a destination path in pCloud.

Instructions

Copy a folder to another location in pCloud.

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>",
      "toPath": "<toPath>"
    },
    "name": "pcloud_copy_folder"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Path of the folder to copy
`toPath`	Yes	Destination folder path

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action without explaining recursion, overwrite behavior, or what happens when the destination exists, which are important for a copy operation.

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 no redundant words. It is front-loaded with the verb and resource, making it easy to parse quickly.

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 copy operation with no annotations or output schema, the description lacks crucial behavioral details such as whether the folder contents are copied, handling of existing destinations, and return value. The schema covers parameters but not behavior, leaving the description incomplete for a mutation tool.

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 covers both parameters at 100%, so the baseline is 3. The description adds no additional semantics beyond the schema's 'path' and 'toPath' descriptions, but it does not need to compensate.

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 clearly states the action (copy) and resource (folder) with a destination, distinguishing it from sibling tools like pcloud_copy_file and pcloud_rename_folder. It is specific and unambiguous.

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?

The description gives no guidance on when to use this tool versus alternatives such as pcloud_copy_file or pcloud_move_folder. It does not mention conditions, prerequisites, or exclusions, leaving the choice entirely to the agent's inference.

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

Deploy Server