Skip to main content
Glama
Sign In
Proton Suite Agent

Proton Suite Agent

by Soluciones-Alexendros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Upload staging to Proton Drive

proton_drive_upload

Uploads the contents of a local staging directory to a remote Proton Drive path, syncing files via the proton-drive CLI.

Instructions

Uploads the local staging directory to a remote Proton Drive path using the proton-drive CLI.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proton_drive_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
local_pathNoOverride staging directory locally.
remote_pathNoRemote destination path on Proton Drive./my-files

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already indicate non-read-only and non-destructive. Description adds no extra behavioral details like overwrite behavior, recursion, or handling of existing files. The concept of 'staging directory' remains unexplained.

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?

Single sentence, 14 words, entirely front-loaded with the core purpose. No redundant information.

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

Completeness2/5

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

No output schema, so return value is not explained. Missing details on error conditions, required authentication, or behavior on duplicate uploads. Incompletely specifies the operation for a file upload tool.

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%, so the schema already documents both parameters. The description reiterates but does not add significant new meaning beyond saying local_path overrides the default staging directory.

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?

Clearly states verb (uploads) and resource (local staging directory to remote Proton Drive path). Mentions CLI. Distinguishes from sibling tools like proton_drive_download (downloads) and proton_drive_copy (copies within drive).

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

Usage Guidelines2/5

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

No explicit guidance on when to use or when not. Lacks prerequisites (e.g., authentication status) and does not differentiate from similar tools like proton_drive_copy for moving files within drive.

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