Skip to main content
Glama
rclone-ui

rclone-mcp

by rclone-ui

sync_bisync

Bidirectional sync between two remote paths with safety controls like dry-run, max-delete limits, and recovery via resync.

Instructions

Bidirectional sync — Performs a bidirectional synchronisation between two paths, supporting safety checks and recovery options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoSet to true to bypass the `maxDelete` safety check.
path1NoFirst remote directory, e.g. `drive:path1`.
path2NoSecond remote directory, e.g. `drive:path2`.
_asyncNoRun the command asynchronously. Returns a job id immediately.
_groupNoAssign the request to a custom stats group.
dryRunNoSet to true to simulate the bisync run without making changes.
resyncNoSet to true to perform a one-time resync, rebuilding bisync history.
_configNoJSON encoded config overrides applied for this call only.
_filterNoJSON encoded filter overrides applied for this call only.
workdirNoDirectory path used to store bisync working files.
checkSyncNoControls final listing comparison; leave true for normal verification or set false to skip.
maxDeleteNoAbort the run if deletions exceed this percentage (default 50).
noCleanupNoSet to true to keep bisync working files after completion.
resilientNoSet to true to allow retrying after certain recoverable errors.
backupdir1NoBackup directory on the first remote for changed files.
backupdir2NoBackup directory on the second remote for changed files.
checkAccessNoSet to true to abort if `RCLONE_TEST` files are missing on either side.
filtersFileNoPath to an rclone filters file applied to both paths.
checkFilenameNoOverride the access-check sentinel filename; defaults to `RCLONE_TEST`.
removeEmptyDirsNoSet to true to remove empty directories during cleanup.
createEmptySrcDirsNoSet to true to mirror empty directories between the two paths.
ignoreListingChecksumNoSet to true to ignore checksum differences when comparing listings.
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only vaguely mentions 'safety checks and recovery options' without explaining what they entail (e.g., maxDelete threshold, resync, backup directories). Key operational details are missing, limiting the agent's understanding of the tool's behavior.

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?

The description is a single efficient sentence, front-loading the core purpose and key features. No wasted words; every phrase earns its place.

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 tool with 22 parameters and no output schema, the description is too minimal. It fails to explain the overall workflow (e.g., working directory, listing comparison, async behavior) or what the tool returns. The agent would need to rely heavily on schema descriptions, which is insufficient for strategic decision-making.

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 22 parameters already described. The description adds no additional meaning or context for parameters; it merely alludes to 'safety checks' without linking to specific params like maxDelete or checkSync. Baseline score of 3 is appropriate given high schema coverage.

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 'Bidirectional sync' and 'bidirectional synchronisation between two paths', with a specific verb and resource. This distinguishes it from one-way sync siblings like sync_copy and sync_move, making its purpose unmistakable.

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?

The description implies usage when two-way synchronization is needed, but does not explicitly state when to use it over alternatives like sync_sync or provide any 'when-not' guidance. The context is implied but not clearly articulated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rclone-ui/rclone-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server