Pause one or more qBittorrent torrents by hash, or pause all active transfers at once.
Pause one or more torrents. Use 'all' to pause everything.
| Name | Required | Description | Default |
|---|---|---|---|
| hashes | Yes | Torrent hash(es), pipe-separated (e.g. 'abc123|def456') or 'all' |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Pause' implies a reversible, non-destructive state change, but the description does not confirm this, explain effects on active connections or seeding, or mention permissions. It adds very little beyond the verb.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two economical sentences with zero filler and the primary action front-loaded. Every word is useful for an agent deciding how to call the tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with no output schema, the description covers the essential action and the 'all' shorthand. However, it omits expected behavior, reversibility, and error handling (e.g., invalid hash), which would be valuable given the absence of annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the parameter schema already explains the pipe-separated hash format and 'all'. The description adds no new syntax or format details, but with full schema coverage the baseline is 4. The schema handles the heavy lifting effectively.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('pause') and resource ('one or more torrents'), making the action immediately clear. It does not explicitly differentiate from sibling tools like 'qbittorrent_resume_torrents' or 'qbittorrent_delete_torrents', though the operation itself is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides handing for the 'all' value, which is a usage hint, but does not state when to use pause versus alternatives like resume or delete. The context is implied by naming the exact operation, meeting the minimum viable level.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.