mcp-pcloud

pcloud_copy_file

Copy a file to another location in pCloud storage. Specify the source file path and destination folder to create a duplicate.

Instructions

Copy a file 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_file"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.3/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 says 'copy', which implies a new file creation, but does not disclose overwrite behavior, required directory existence, access permissions, or return value. This is minimal intent without operational detail.

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, front-loaded sentence that states the operation without unnecessary words. It is appropriately concise for the simplicity of the tool.

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?

Given the low complexity (two required parameters, no output schema, no annotations), the description is minimally adequate but lacks behavioral details such as what happens if the destination exists or what is returned. These gaps prevent a higher score, though the schema covers parameter semantics.

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 provides complete descriptions for both parameters (path and toPath, 100% coverage). The description adds no additional parameter semantics, but the schema is sufficient, so a baseline score of 3 is appropriate.

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 uses the verb 'Copy' with the resource 'a file' and specifies 'to another location in pCloud', clearly conveying the operation and distinguishing it from sibling tools like pcloud_copy_folder. It goes beyond the tool name by adding the destination detail.

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 provides no guidance on when to use this tool versus alternatives like pcloud_rename_file or pcloud_copy_folder. There is no mention of prerequisites, conflict behavior, or exclusions, leaving the agent to infer usage solely from the tool name.

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

Deploy Server