Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get item info

drive_info
Read-onlyIdempotent

Retrieve full metadata for a specific Proton Drive file or folder, including revision details, modification and upload times, and a claimed SHA1 hash. Use to inspect a single item's details.

Instructions

Get full metadata for one Proton Drive file or folder, including latest revision details. Also returns mtime (original local modification time), uploadedAt (revision upload time) and sha1 (hash CLAIMED by the uploader: unverified and often absent) when known. Verification wrappers are unwrapped and noise fields dropped (verbose=true returns the raw CLI node, whose shape is not guaranteed). Use drive_list to enumerate children.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute remote path, e.g. /my-files/report.pdf.
verboseNoReturn the raw CLI node instead of the trimmed one (default false).

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/report.pdf"New value: +"Absolute remote path, e.g. /my-files/report.pdf."
  2. Changed1 schema field changedv1.0.38
    • addedInput schema / properties / verbose
      Added value: +{
+  "description": "Return the raw CLI node instead of the trimmed one (default false).",
+  "type": "boolean"
+}
  3. Addedv1.0.28

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and idempotentHint; the description adds substantial behavioral context beyond them — that sha1 is uploader-claimed, unverified and often absent, that verification wrappers are unwrapped and noise fields dropped, and that verbose=true returns a raw CLI node with no guaranteed shape.

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?

Front-loaded with the core purpose and tightly packed with useful detail; the parenthetical on verbose and the sha1 caveat both earn their place. Slightly dense, but no sentence is 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?

There is no output schema, so the description carries the return-value burden and does so by naming the specific fields returned (mtime, uploadedAt, sha1) and their caveats. An agent has everything needed to call and interpret the result.

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%, so the baseline is 3, but the description adds real meaning to verbose by explaining it returns an unguaranteed raw CLI node versus the trimmed default. The path parameter adds nothing beyond the schema's own example, so it is not a full 5.

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?

Names a specific verb and resource ('Get full metadata for one Proton Drive file or folder') and scopes it to a single item, with a closing pointer to drive_list for enumeration. An agent can distinguish it from the many sibling drive tools without opening the schema.

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?

Explicitly routes enumeration to drive_list, which is the key adjacent use case. It does not address when to prefer this over drive_read_file/drive_read_content, but for a metadata-only read tool the guidance is clear enough.

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