Skip to main content
Glama

drive_upload

Upload local files or folders to Proton Drive with end-to-end encryption. Preserves folder structure and handles conflicts by skipping, overwriting, or renaming.

Instructions

Upload a local file or folder to Proton Drive with end-to-end encryption. Requires authentication. For folders, uploads recursively and preserves directory structure. Returns {uploaded, skipped, failed} counts — fails the call if failed > 0 (common causes: quota exceeded, destination path not found, permission denied). conflictStrategy defaults to 'skip' — only use 'overwrite' with explicit user confirmation since it permanently replaces the remote file. Do not use to move files already on Drive (use drive_move) or to write text content directly (use drive_write_file if PROTON_DRIVE_SYNC_PATH is set). Ensure destination folder exists first with drive_list; create it with drive_mkdir if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localPathYesAbsolute local filesystem path of the file or folder to upload (must start with '/').
remotePathYesAbsolute remote Drive destination folder path (must start with '/'). E.g. /my-files/Reports
conflictStrategyNo'skip' leaves existing remote files unchanged (default). 'overwrite' permanently replaces the remote file — confirm with user first. 'rename' uploads with a unique name to avoid conflicts.
Behavior5/5

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

Discloses key behaviors: recursive upload for folders, preserving directory structure, return format with counts, failure conditions (quota, path issues), conflictStrategy defaults to 'skip', and permanent replacement for 'overwrite'. This adds substantial context beyond the sparse openWorldHint annotation.

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 description is somewhat long but each sentence provides necessary information. It is front-loaded with the main action and organized logically. Could be slightly more concise, but still efficient.

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, the description covers return format, failure modes, prerequisites, and sibling tool guidance. It provides enough detail for an agent to invoke the tool correctly and handle outcomes.

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 baseline is 3. The description adds value by noting localPath must start with '/', giving an example for remotePath, and explaining conflictStrategy defaults and overwrite caution. This extra context justifies a 4.

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 tool uploads a local file or folder to Proton Drive with end-to-end encryption. It distinguishes from siblings like drive_move and drive_write_file, making the purpose unambiguous.

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?

Explicitly provides when to use (upload local content), when not to use (moving files or writing text), prerequisites (ensure destination folder exists), and cautions about conflictStrategy 'overwrite' needing user confirmation. Also directs to drive_list and drive_mkdir for folder creation.

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

Install Server

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