Skip to main content
Glama
Sign In
rclone-mcp

rclone-mcp

by rclone-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

operations_purge

Purge a remote directory or container and all its contents by specifying the remote name and path.

Instructions

Purge directory — Deletes a directory or container and all of its contents.

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

Input Schema

NameRequiredDescriptionDefault
fsNoRemote name or path from which to remove all contents.
_asyncNoRun the command asynchronously. Returns a job id immediately.
_groupNoAssign the request to a custom stats group.
remoteNoPath within `fs` whose contents should be purged.
_configNoJSON encoded config overrides applied for this call only.
_filterNoJSON encoded filter overrides applied for this call only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It states that the tool deletes contents but does not disclose safety checks, irreversibility, asynchronous behavior (_async param), or that it affects remote paths. The description is minimal on behavioral traits beyond the basic action.

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?

The description is a single sentence, very concise. It earns its place by stating the core purpose but lacks structure or additional details. It is not verbose, but could be slightly more informative without losing conciseness.

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?

Given the tool has 6 parameters, is destructive, no annotations, and no output schema, the description is insufficient. It does not explain parameter relationships, safety warnings, or behavior like async. The context is incomplete for safe and effective use.

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 all parameters described. The tool description adds no extra meaning beyond the schema; for example, it does not explain how fs and remote interact. Baseline 3 is appropriate as the description does not detract but adds no value over the schema.

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 'Purge directory — Deletes a directory or container and all of its contents.' clearly specifies the verb (purge/delete) and resource (directory/container and all contents), distinguishing it from siblings like operations_delete (file) or operations_rmdir (empty directory).

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?

The description provides no guidance on when to use this tool versus alternatives such as operations_delete, operations_rmdir, or operations_cleanup. There is no indication of prerequisites or appropriate contexts.

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