Skip to main content
Glama

drive_download

Download files or folders from Proton Drive to your local machine. Specify a destination folder; remote items keep their original names. Handles conflicts via skip, rename, or remove options.

Instructions

Download a file or folder from Proton Drive to the local filesystem. Requires authentication. localPath is a destination FOLDER, not the file's exact final path — the CLI creates it automatically if missing and places the downloaded item inside it under its original remote name. E.g. downloading /my-files/report.pdf with localPath '/tmp/out' produces /tmp/out/report.pdf, not /tmp/out itself as a file — confirmed live against the real CLI (v0.8.0). For folders, downloads recursively. Conflict strategies are set separately for files and folders (CLI v0.8.0+) — both default to 'skip'. Returns {downloaded} count — not the actual local path; construct it as localPath + the remote item's basename if you need it. Do not use to move files within Drive (use drive_move) or to read a small text file's contents (use drive_read_file if PROTON_DRIVE_SYNC_PATH is set).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localPathYesAbsolute local DESTINATION FOLDER (must start with '/'), not the file's final path. Created automatically if it doesn't exist. The downloaded item is placed inside it, keeping its original remote name.
remotePathYesAbsolute remote Drive path to download (must start with '/'). E.g. /my-files/report.pdf
fileConflictStrategyNo'skip' leaves an existing local file unchanged (default). 'rename' downloads under a unique name. 'remove' deletes the local file and downloads the remote copy in its place — confirm with user first.
folderConflictStrategyNo'skip' leaves an existing local folder unchanged (default). 'merge' merges the downloaded folder's contents into the existing one. 'rename' downloads under a unique name. 'remove' deletes the local folder and downloads the remote copy in its place — confirm with user first.
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

With only openWorldHint in annotations, the description carries the full behavioral burden and fully delivers: it explains the destination-folder semantics, automatic folder creation, original-name preservation, recursive folder downloads, file/folder conflict defaults, version-specific behavior, and that the return value is {downloaded} not the path. No contradictions with annotations.

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?

Though long, the description is dense and every sentence earns its place: purpose, critical path semantics, example, recursion, conflict defaults, return-value caveat, and exclusions. Critical info is front-loaded before the caveats.

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

Completeness5/5

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

Given no output schema and sparse annotations, the description is remarkably complete: authentication, path construction, recursive behavior, conflict strategy defaults, return type, version context, and clear routing to sibling tools. An agent has everything needed to call correctly and interpret results.

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% and the schema already documents localPath and conflict strategies well. The description still adds value with a concrete example (/my-files/report.pdf + /tmp/out → /tmp/out/report.pdf) and clarifies that conflict strategies are set separately for files and folders with default 'skip'.

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 opens with a specific verb and resource: 'Download a file or folder from Proton Drive to the local filesystem.' It clearly distinguishes itself from similar operations by explicitly naming drive_move and drive_read_file as alternatives for different tasks.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance (downloading to local filesystem) and when-not-to-use guidance: 'Do not use to move files within Drive (use drive_move) or to read a small text file's contents (use drive_read_file if PROTON_DRIVE_SYNC_PATH is set).' It also notes the authentication requirement.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googlarz/proton-drive-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server