Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Sign out

drive_auth_logout
DestructiveIdempotent

Clear the stored Proton Drive session from the OS keychain to log out. File and sharing operations fail until you log in again.

Instructions

Clear the stored Proton Drive session from the OS keychain. All file and sharing operations fail afterwards until the user runs proton-drive auth login again. Idempotent. Requires confirmed=true after explicit user approval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructive and idempotent, but description adds key behavioral details: session is cleared from OS keychain, file/sharing ops fail until login, and confirmed=true is required after explicit user approval. No contradiction.

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?

Four short sentences, front-loaded with the action and consequence. The standalone 'Idempotent' sentence partly repeats the annotation, a minor redundancy, but overall efficient.

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 one-parameter auth logout with annotations covering safety traits and no output schema, description provides necessary postcondition and approval requirement. Complete for agent invocation.

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%; the confirmed parameter is fully documented in the schema. Description reinforces the approval requirement but adds no format or syntax beyond the schema; 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?

States a specific verb ('Clear') and resource ('stored Proton Drive session from the OS keychain'), plus the postcondition that all file and sharing operations fail until login. Distinguishable from sibling auth/status tools by name and scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly situates use: sign out, requires explicit user approval and confirmed=true; warns operations fail until login. Does not explicitly name alternatives such as drive_auth_status or when not to use, so not a 5.

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