Skip to main content
Glama
Sign In
Proton Suite Agent

Proton Suite Agent

by Soluciones-Alexendros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Remove files from Proton Drive

proton_drive_remove
DestructiveIdempotent

Permanently delete a remote file or folder from Proton Drive. This action cannot be undone.

Instructions

Permanently removes a remote path from Proton Drive. Destructive operation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "remote_path": "<remote_path>"
    },
    "name": "proton_drive_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
remote_pathYesRemote path to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true, and the description adds 'Permanently removes' and 'Destructive operation', reinforcing irreversible behavior. No mention of permissions or side effects, but adequate for a simple deletion.

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?

Two concise sentences: first states the action, second emphasizes destructive nature. Front-loaded with no extraneous information.

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 single-parameter remove tool with full schema coverage and annotations, the description sufficiently conveys permanence and destructiveness. No output schema needed.

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% with a clear 'remote_path' parameter description. The tool description adds no additional meaning beyond what the schema provides.

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?

The description clearly states 'Permanently removes a remote path from Proton Drive' with a specific verb and resource, distinguishing it from sibling tools like delete_email or move operations.

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 guidance on when to use this tool versus alternatives (e.g., move, share) or prerequisites like ensuring correct path. The description only states the action.

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