qbt-kit

move_torrents

Move torrent data to a new directory via qBittorrent while keeping torrents valid; the call returns before completion, and optional recheck verifies pieces afterward.

Instructions

Move a torrent's data to a new location. qBittorrent performs the move and the torrent stays valid; the call returns before the move finishes. A recheck afterwards is optional because it rehashes everything.

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": {
      "hashes": "<hashes>",
      "location": "<location>"
    },
    "name": "move_torrents"
  }
}

Input Schema

Name	Required	Description
`hashes`	Yes	torrent hashes
`recheck`	No	verify against piece hashes afterwards; slow on large data
`location`	Yes	destination directory

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses important traits: qBittorrent performs the move asynchronously, the call returns before completion, and the torrent remains valid. It does not cover permissions, destination conflicts, failure behavior, or whether existing data at the destination is overwritten, leaving some mutation-related gaps.

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 three tight sentences with the core action front-loaded. Each sentence adds useful information about behavior or the optional recheck, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema reduces the need to explain return values, and the description covers the key async behavior and torrent validity. It still omits some operational details relevant to a mutation tool with no annotations, such as destination requirements and conflict handling.

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 parameters are already documented clearly. The description reinforces that recheck is optional and rehashes data, but it does not add substantial meaning beyond the schema beyond that rationale.

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 states a specific verb and resource: moving a torrent's data to a new location. It clearly distinguishes this action from sibling tools like add_torrent, delete_torrents, and control_torrents, which do not move existing data.

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 gives some usage guidance by saying a recheck afterwards is optional and why, but it does not explicitly say when to use move_torrents versus alternatives or describe prerequisites. The intended use is implied by the clear purpose rather than stated with explicit comparisons.

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

This server cannot be deployed