Skip to main content
Glama
Sign In
rclone-mcp

rclone-mcp

by rclone-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

operations_cleanup

Permanently delete trashed files from cloud storage to free up space and maintain a clean remote directory.

Instructions

Remove trashed files — Permanently removes trashed objects from the specified remote path.

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": "operations_cleanup"
  }
}

Input Schema

NameRequiredDescriptionDefault
fsNoRemote name or path to clean up, for example `drive:`.
_asyncNoRun the command asynchronously. Returns a job id immediately.
_groupNoAssign the request to a custom stats group.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. States 'permanently removes' indicating destructiveness, but lacks details on reversibility, permissions required, or any side effects. Adequate but not rich.

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?

Single sentence, concise and front-loaded. Could include more structured info like typical usage, but remains efficient and focused.

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?

For a potentially dangerous operation, description is minimal. No details on prerequisites, scope (single file vs batch), or warnings beyond 'permanently'. Incomplete given many sibling tools.

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%, so baseline is 3. Description adds no extra parameter information beyond what schema provides (e.g., no details on _async or _group).

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 the action ('Remove trashed files') and the resource ('trashed objects from the specified remote path'). Distinguishes from sibling tools like operations_delete and operations_purge by specifying 'trashed' files.

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. Does not mention exclusions or prerequisites, nor any context about cleaning up trash versus other deletion operations.

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