Proton Suite Agent

Download from Proton Drive to staging

proton_drive_download

Download a Proton Drive remote path into the local staging directory for offline access or syncing. Re-running is idempotent, so files stay consistent.

Instructions

Downloads a remote Proton Drive path into the local staging directory using the proton-drive CLI. Idempotent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proton_drive_download"
  }
}

Input Schema

Name	Required	Description	Default
`local_path`	No	Override staging directory locally. Defaults to configured stagingDir.
`remote_path`	No	Remote path on Proton Drive to download.	/my-files

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.0Jul 28, 2026

TDQS

C2.7/5.0

Behavior1/5

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

The description asserts 'Idempotent' while the annotations declare idempotentHint=false, a direct contradiction about a behaviorally significant property. It also omits auth requirements and overwrite behavior for an existing local file, and the annotation set does not cover those gaps.

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?

Two short, front-loaded sentences with no filler; the core action leads and the qualifier trails. The trailing sentence is wasted space only because its content is incorrect.

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?

No output schema and no annotations describing safety of the local write, so the description should explain where files land, what happens on collision, and whether credentials are required. It covers none of this, and the one behavioral claim it makes is wrong.

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?

Schema description coverage is 100% and both parameters are documented in-schema (stagingDir default, remote_path default '/my-files'), so the baseline is 3. The description restates the local/remote split but adds no format, path-resolution, or override details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Downloads a remote Proton Drive path into the local staging directory using the proton-drive CLI.' That is enough to separate it from proton_drive_upload or proton_drive_copy, though it never names a sibling or explicitly contrasts with them.

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?

No when-to-use guidance, no prerequisites (e.g. that proton_drive_auth_login/proton_bridge_login must have run first), and no mention of alternatives such as proton_drive_list_files to discover a valid remote_path before downloading.

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

Deploy Server