Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Restore from trash

drive_restore

Restore a trashed file or folder to its original Proton Drive path using a trash path or uid from drive_list_trash. Refuses ambiguous same-name items.

Instructions

Restore a trashed file or folder to its original Proton Drive path. Find the path or uid with drive_list_trash. If several trashed items share the name, this refuses and lists their uids: the CLI can only address trashed items by name, so use the Proton Drive web or desktop app for that. Fails if the original parent is gone or a same-named item now exists at that path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidNoTrash uid from drive_list_trash; if path is also given they must match.
pathNoTrash path from drive_list_trash. Give path or uid (or both).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • changedInput schema / properties / path / description
      Previous value: -"Absolute remote Drive path of the item to restore, as shown in drive_list_trash output (must start with '/')."New value: +"Trash path from drive_list_trash. Give path or uid (or both)."
    • addedInput schema / properties / uid
      Added value: +{
+  "description": "Trash uid from drive_list_trash; if path is also given they must match.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "path"
-]New value: +[]
  2. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / path / description
      Previous value: -"Remote Drive path to restore."New value: +"Absolute remote Drive path of the item to restore, as shown in drive_list_trash output (must start with '/')."
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations give only destructiveHint=false, so the description carries the real load: it discloses the refusal on duplicate names, the CLI's name-only addressing limitation, and two failure conditions (original parent gone, same-named item at the target path).

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?

Three tight sentences, front-loaded with the action and its scope; the constraints and alternative follow in order of relevance, with no filler.

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 two-optional-parameter restore tool with no output schema, the description covers what an agent needs to call it correctly and what will make the call fail.

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 already documented, including the path/uid match rule. The description adds only the contextual note that the CLI addresses trashed items by name, so baseline 3 is appropriate.

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 ('restore') and resource ('trashed file or folder') plus the destination ('original Proton Drive path'), which cleanly separates it from siblings like drive_trash, drive_empty_trash, and drive_delete.

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 routes the agent to drive_list_trash to obtain the path/uid, and names a genuine alternative (Proton Drive web or desktop app) for the ambiguous-name case where this tool refuses.

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