Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Leave shared item

drive_share_leave
Destructive

Leave a Proton Drive folder shared with you without affecting the owner or other members. Requires confirmed=true after explicit user approval.

Instructions

Leave a Proton Drive folder shared with you; the owner and other members are unaffected. For your own folders use drive_share_revoke. Requires confirmed=true after explicit user approval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute remote Drive path of the shared folder to leave (must start with '/'). E.g. /shared-with-me/project
confirmedNoMust be true; only after the user approved this exact action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  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. Addedv1.0.26

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, but the description adds valuable context the annotation cannot: the blast radius (owner and other members unaffected) and the approval-gated confirmation requirement. It stops short of describing failure modes (e.g. what happens if path isn't a shared folder or isn't owned by someone else).

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 clauses: action+scope, alternative routing, and prerequisite. Zero waste, and the action is front-loaded before the routing advice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter mutation with no output schema, the description covers purpose, routing, blast radius, and the confirmation gate. Only minor gaps remain (error behavior if path is not a shared folder), which is defensible given the rich schema text.

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 coverage is 100%, so both parameters including path format and the confirmed semantics are already fully documented in the schema. The description reinforces the confirmed requirement but adds no syntax or format detail beyond it, matching the baseline 3.

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?

Specific verb+resource ('Leave a Proton Drive folder shared with you') with an explicit scope boundary stating the owner and other members are unaffected. It also names the sibling it is not (drive_share_revoke), so an agent can distinguish it immediately.

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: 'For your own folders use drive_share_revoke', and states the prerequisite 'Requires confirmed=true after explicit user approval.' Both when-to-use and the alternative are named.

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