Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Write synced text file

drive_write_file
Destructive

Write UTF-8 text up to 5 MB to a file in the local Proton Drive sync folder; creates parent folders and needs confirmed=true to overwrite existing files. Desktop app syncs it to the cloud.

Instructions

Write text (max 5 MB) to a file in the local Proton Drive sync folder; no Proton login needed. Requires PROTON_DRIVE_SYNC_PATH; the desktop app must be running to sync it to the cloud. Creates parent directories locally. Refuses to overwrite an existing file unless confirmed=true — ask the user first. For binary content use drive_upload. Requires confirmed=true when the file already exists (it would be overwritten).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute remote Drive path of the file to write (must start with '/'). /my-files/<rest> maps to <PROTON_DRIVE_SYNC_PATH>/<rest>; only /my-files is synced, other Drive roots are rejected. A path not starting with a Drive root is taken relative to the sync folder. E.g. /my-files/notes.txt
contentYesUTF-8 text content to write. The file will be created or overwritten.
confirmedNoMust be true; only after the user approved this exact action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / confirmed / description
      Previous value: -"Must be true. Only set after the user explicitly approved this exact action."New value: +"Must be true; only after the user approved this exact action."
    • changedInput schema / properties / path / description
      Previous value: -"Absolute remote Drive path of the file to write (must start with '/'). Mapped to the local sync folder. E.g. /my-files/notes.txt"New value: +"Absolute remote Drive path of the file to write (must start with '/'). /my-files/<rest> maps to <PROTON_DRIVE_SYNC_PATH>/<rest>; only /my-files is synced, other Drive roots are rejected. A path not starting with a Drive root is taken relative to the sync folder. E.g. /my-files/notes.txt"
  2. Changed1 schema field changedv1.0.38
    • addedInput schema / properties / confirmed
      Added value: +{
+  "description": "Must be true. Only set after the user explicitly approved this exact action.",
+  "type": "boolean"
+}
  3. Addedv0.1.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare destructiveHint and openWorldHint; the description adds the substantive context they don't: the 5 MB cap, that no Proton login is needed, the required local env var, the dependency on the running desktop app for cloud sync, local parent-directory creation, and the refuse-to-overwrite safeguard. This is exactly the extra behavioral layer expected when annotations cover only the safety flags.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and generally tight, but the overwrite rule is stated twice — 'Refuses to overwrite an existing file unless confirmed=true — ask the user first' and 'Requires confirmed=true when the file already exists (it would be overwritten)' — so one sentence is pure duplication.

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?

For a mutation tool with no output schema, the description covers the environment prerequisites, size limit, path scoping behavior, and the confirmation gate, which is everything an agent needs to invoke it safely. The annotated destructive/open-world hints are also consistent with the described overwrite behavior.

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, but the description adds workflow meaning the schema doesn't: confirmed must be supplied when the file already exists because it would be overwritten, and the agent should get user approval first. It doesn't restate path syntax (correctly deferring to the schema), so it stays additive rather than redundant.

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 ('Write text ... to a file in the local Proton Drive sync folder') and immediately scopes it against siblings by naming drive_upload for binary content and implying drive_read_file is the read counterpart. An agent can distinguish it from drive_mkdir, drive_upload and drive_rename without opening any schema.

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?

Explicit when-to-use and when-not: text only (max 5 MB), use drive_upload for binary, requires the desktop app running and PROTON_DRIVE_SYNC_PATH set, and must not overwrite without user approval. It also tells the agent to ask the user first, which is a usable behavioral rule.

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