Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Copy item

drive_copy

Copy files or folders on Proton Drive while keeping the original; set destinationPath as the target parent folder and use newName to duplicate an item in its own folder.

Instructions

Copy a file or folder on Proton Drive; the original stays. destinationPath is the target PARENT folder (unlike drive_move, which takes a full new path). Pass newName to copy under a different name — required to duplicate an item inside its own folder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
newNameNoOptional name for the copy (CLI --name). Required to copy an item into its own folder.
sourcePathYesAbsolute remote path to copy.
destinationPathYesAbsolute remote target PARENT folder, e.g. /my-files/Archive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / destinationPath / description
      Previous value: -"Absolute remote Drive path of the target parent folder (must start with '/'). E.g. /my-files/Archive"New value: +"Absolute remote target PARENT folder, e.g. /my-files/Archive."
    • changedInput schema / properties / sourcePath / description
      Previous value: -"Absolute remote Drive path of the file or folder to copy (must start with '/'). E.g. /my-files/report.pdf"New value: +"Absolute remote path to copy."
  2. Changed1 schema field changedv1.0.38
    • addedInput schema / properties / newName
      Added value: +{
+  "description": "Optional name for the copy (CLI --name). Required to copy an item into its own folder.",
+  "type": "string"
+}
  3. Addedv1.0.26

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description reinforces that the original stays, but that is largely redundant with destructiveHint=false, and it does not add richer behavioral details such as permission requirements, overwrite/collision behavior, or rate limits.

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 compact and front-loaded: copy action first, behavioral note second, parameter distinctions third. Every sentence adds relevant selection or invocation context with no wasted prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given full schema coverage, existing annotations, and no output schema, the description covers the essential copy semantics and sibling-tool distinction. It is nearly complete, though collision behavior and permission expectations for a non-idempotent copy are not addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds useful semantic contrast by explaining that destinationPath is a target PARENT folder unlike drive_move, and reinforces that newName is required when duplicating inside the same folder.

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?

States a specific verb and resource ('Copy a file or folder on Proton Drive'), clarifies the non-mutating effect ('the original stays'), and explicitly distinguishes drive_copy from drive_move. An agent can identify the correct operation without opening sibling schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear usage context: destinationPath is a parent folder, unlike drive_move, and newName is required to duplicate an item inside its own folder. It does not enumerate when-not-to-use cases, but the alternative and key conditional usage are explicit.

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