Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Show sharing status

drive_share_status
Read-onlyIdempotent

Check the sharing status of a Proton Drive file or folder before inviting or revoking access: see if shared, list members (including pending), and get share URL.

Instructions

Return the sharing state of a Proton Drive path: {isShared, members: [{email, role, addedAt?, status: 'accepted'|'pending'}], shareUrl?}. members includes pending invitations, including to non-Proton addresses — check status. Call before drive_share_invite (avoid duplicates) and drive_share_revoke (confirm the email). Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute remote path of an existing file or folder, e.g. /my-files/project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / path / description
      Previous value: -"Absolute remote Drive path to inspect (must start with '/'). E.g. /my-files/project or /my-files/report.pdf. Must be an existing file or folder on Proton Drive."New value: +"Absolute remote path of an existing file or folder, e.g. /my-files/project."
  2. Changed1 schema field changedv1.0.23
    • changedInput schema / properties / path / description
      Previous value: -"Absolute remote Drive path to inspect (must start with '/')."New value: +"Absolute remote Drive path to inspect (must start with '/'). E.g. /my-files/project or /my-files/report.pdf. Must be an existing file or folder on Proton Drive."
  3. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / path / description
      Previous value: -"Remote Drive path to check sharing for."New value: +"Absolute remote Drive path to inspect (must start with '/')."
  4. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description's 'Read-only' restates the structured field. What it adds is genuinely useful and not in the annotations: that members includes pending invitations, possibly to non-Proton addresses, and that the status field must be checked to interpret them.

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?

One dense but well-front-loaded block: return shape first, then the pending-invitation caveat, then the usage rule. Every clause carries information an agent needs, 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?

With no output schema, the description carries the burden of describing return values and does so explicitly (isShared, members with email/role/addedAt/status, shareUrl). Combined with annotations covering safety and the schema covering the single parameter, nothing an agent needs to call it correctly is missing.

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% and the path parameter is fully documented in the schema, including format and example, so the description does not need to explain it. The description adds no additional parameter meaning beyond what the schema already provides; baseline 3 applies.

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+resource ('Return the sharing state of a Proton Drive path') and enumerates the returned shape, so the agent knows exactly what it gets. It also names the siblings it relates to (drive_share_invite, drive_share_revoke), making it distinguishable without opening other schemas.

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 prescribes ordering and purpose: call before drive_share_invite to avoid duplicates and before drive_share_revoke to confirm the email address. Both the when and the why are stated, with the alternative tools 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