Skip to main content
Glama

drive_write_file

Destructive

Write text content to a file in the local Proton Drive sync folder. Creates parent directories if missing and syncs to cloud when the desktop app is running.

Instructions

Write text content to a file in the local Proton Drive sync folder. Requires authentication. Requires the PROTON_DRIVE_SYNC_PATH environment variable to point to the sync folder root. The Proton Drive desktop app must be running to sync the written file to the cloud. Creates parent directories locally if they do not exist. Overwrites the file if it already exists — confirm with the user before overwriting. Do not use for binary content or files that need to be uploaded without the desktop app running — use drive_upload instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute remote Drive path of the file to write (must start with '/'). Mapped to the local sync folder. E.g. /my-files/notes.txt
contentYesUTF-8 text content to write. The file will be created or overwritten.
Behavior5/5

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

Adds important behavioral context beyond annotations: confirms overwriting with user, creates parent directories locally, and requires desktop app. No contradiction with destructiveHint and openWorldHint.

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?

Concise with no wasted words; front-loaded with purpose, then prerequisites, behavior, and caveats in logical order.

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?

Complete for a 2-param tool without output schema: covers purpose, requirements, side effects, and usage boundaries.

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%, baseline 3. Description adds context for path (mapped to local folder) and content (UTF-8), providing extra meaning over schema descriptions.

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 verb 'write' and resource 'file' within the Proton Drive sync folder context, and it distinguishes from drive_upload by specifying not to use for binary content or without desktop app.

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 mentions when to use (text content, with app running) and when not to (binary, without app) with the alternative drive_upload, plus prerequisites like authentication and environment variable.

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