Skip to main content
Glama
jabberjabberjabber

qBittorrent MCP Server

pause_torrent

Pause active torrent downloads to temporarily stop data transfer and conserve bandwidth or system resources.

Instructions

Pause a torrent.

Args: torrent_hash: Hash of the torrent to pause

Returns: Status message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
torrent_hashYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:220-238 (handler)
    The pause_torrent tool handler function, decorated with @mcp.tool() for registration. It pauses the specified torrent using the qBittorrent client and returns a status dictionary.
    @mcp.tool()
    def pause_torrent(torrent_hash: str) -> dict[str, str]:
        """
        Pause a torrent.
    
        Args:
            torrent_hash: Hash of the torrent to pause
    
        Returns:
            Status message
        """
        client = get_qbt_client()
    
        try:
            client.torrents_pause(torrent_hashes=torrent_hash)
            return {"status": "success", "message": f"Torrent {torrent_hash} paused"}
        except Exception as e:
            return {"status": "error", "message": str(e)}
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Pause a torrent' implies a state change operation, it doesn't disclose whether this requires specific permissions, whether pausing is reversible, what happens to partially downloaded data, or any rate limits. The description adds minimal behavioral context 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 appropriately concise with a clear purpose statement followed by Args and Returns sections. The structure helps scanning, though the 'Returns' section is somewhat redundant given the output schema exists. Every sentence serves a purpose with minimal waste.

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

Completeness3/5

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

For a single-parameter mutation tool with no annotations, the description is minimally adequate. The output schema exists, so return values don't need explanation. However, as a state-changing operation, the description should provide more behavioral context about what pausing entails and any side effects, which it lacks.

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 0%, so the schema provides no parameter documentation. The description adds that 'torrent_hash' is the 'Hash of the torrent to pause', which provides basic semantic meaning. However, it doesn't explain hash format, length, or where to obtain it, leaving significant gaps in parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with 'Pause a torrent' - a specific verb (pause) and resource (torrent). It distinguishes from siblings like 'resume_torrent' and 'delete_torrent' by specifying the pause action. However, it doesn't explicitly differentiate from all siblings in the description text itself.

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. It doesn't mention when to pause versus resume or delete a torrent, nor does it provide any context about prerequisites or appropriate situations for pausing. The agent must infer usage from the tool name alone.

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/jabberjabberjabber/qbit-mcp'

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