rclone-mcp

operations_movefile

Move a single file from one remote path to another. Specify source and destination remotes and paths to transfer the object.

Instructions

Move a single file — Moves one object from a source remote and path to a destination remote and 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_movefile"
  }
}

Input Schema

Name	Required	Description
`dstFs`	No	Destination remote name or path where the file will be moved.
`srcFs`	No	Source remote name or path containing the file to move.
`_async`	No	Run the command asynchronously. Returns a job id immediately.
`_group`	No	Assign the request to a custom stats group.
`dstRemote`	No	Destination path within `dstFs` for the moved object.
`srcRemote`	No	Path to the source object within `srcFs`.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 26, 2026

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 full burden. It states the tool 'moves' an object but does not disclose whether it is atomic, what happens if the destination exists, whether the source is deleted immediately, or any error conditions.

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 with a clear subject and action, but it redundantly repeats 'Move a single file' before the explanation. It is efficient but could be more concise.

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 6 parameters (none required), no output schema, and no annotations, the description lacks context about parameter relationships (e.g., srcFs vs srcRemote), optional flags like _async and _group, and whether directory moves are allowed despite the name 'file'.

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 description coverage is 100%, so the schema already documents each parameter. The tool description adds no additional meaning beyond what the schema provides, meeting the baseline expectation.

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 the verb 'move' and resource 'file/object', and the tool name 'operations_movefile' distinguishes from sibling tools like 'operations_copyfile' and 'operations_deletefile'. The phrase 'single file' further clarifies scope.

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 is provided on when to use this tool versus alternatives (e.g., operations_copyfile, sync_move). There are no prerequisites, exclusions, or context for usage.

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

Deploy Server