Skip to main content
Glama
Sign In
Proton Suite Agent

Proton Suite Agent

by Soluciones-Alexendros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Organize files in Proton Drive

proton_drive_organize
Destructive

Analyze a Proton Drive staging directory and move files into type-based folders. Preview changes with dry-run by default, and reject or rename collisions to avoid overwrites.

Instructions

Analyzes the staging directory and moves files into a structured folder layout (by type). Dry-run by default. Never overwrites: colliding destinations are rejected unless strategy="rename".

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_organize"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoIf true, only shows the plan without moving files.
strategyNoWhat to do when the destination is taken: reject (default, no-clobber) or rename (disambiguate).reject
staging_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.1
    • addedInput schema / properties / strategy
      Added value: +{
+  "default": "reject",
+  "description": "What to do when the destination is taken: reject (default, no-clobber) or rename (disambiguate).",
+  "enum": [
+    "reject",
+    "rename"
+  ],
+  "type": "string"
+}
  2. First observedv0.8.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotency, but the description adds real behavioral detail beyond them: dry-run is the default, overwrites are never permitted, and collisions are rejected unless strategy="rename". What is still unstated is what the type-based layout actually maps files to.

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 short sentences, no waste, with the destructive/collision constraint front-loaded after the core action. Every clause carries information the agent needs before invoking.

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 mutation tool with no output schema and 3 parameters, the definition covers the critical decision points: default dry-run, no-clobber semantics, and the rename escape hatch. The main omission is an explanation of the 'by type' folder scheme, which is mitigated by the safe dry-run default.

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 67%: dry_run and strategy are already documented in the schema, and the description only echoes strategy="rename" and the dry-run default. staging_dir has no schema description and the prose only alludes to it as 'the staging directory', so the description does not compensate for that gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource: it analyzes a staging directory and moves files into a type-based folder layout. That scope ('staging directory', 'by type') distinguishes it from generic siblings like proton_drive_move or proton_drive_copy, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

It discloses the operational default ('Dry-run by default'), which implies a safe first-call workflow, but it offers no explicit when-to-use vs proton_drive_move/proton_drive_copy or when-not-to-use guidance. Usage is inferable rather than stated.

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