Skip to main content
Glama
philogicae

rqbit Torrent Client MCP

pause_torrent

Pause an active torrent by providing its ID. Stops data transfer without deleting the torrent, allowing resumption later.

Instructions

Pause a torrent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
torrent_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for 'pause_torrent'. Registers via @mcp.tool() decorator, calls rqbit_client.pause_torrent(), and returns a success/error message.
    @mcp.tool()
    async def pause_torrent(torrent_id: str) -> str:
        """Pause a torrent."""
        logger.info(f"Pausing torrent: {torrent_id}")
        result = await rqbit_client.pause_torrent(torrent_id)
        if isinstance(result, str):
            error = f"Error pausing torrent {torrent_id}: {result}"
            logger.error(error)
            return error
        return "Successfully paused torrent " + torrent_id
  • Registration of 'pause_torrent' as an MCP tool via the @mcp.tool() decorator on line 90 of mcp_server.py.
    @mcp.tool()
    async def pause_torrent(torrent_id: str) -> str:
  • Helper client method that executes the HTTP POST request to /torrents/{id_or_infohash}/pause via the rqbit API.
    async def pause_torrent(self, id_or_infohash: str) -> None | str:
        """Pause a torrent."""
        return await self._safe_request("POST", f"/torrents/{id_or_infohash}/pause")
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits, but it only states the action without mentioning side effects, permission requirements, or reversibility. The agent gains no insight into what happens after pausing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence) but lacks detail. While not verbose, it is minimally informative and could benefit from a brief elaboration without losing conciseness.

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 the simplicity of the tool (one parameter), the description is incomplete—it does not mention the output schema or indicate what the response signifies (e.g., success/failure). The agent lacks closure on expected results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter 'torrent_id' is not explained beyond its type. With 0% schema description coverage, the description adds no meaning; the agent must infer from context that it identifies the torrent.

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 'Pause a torrent' clearly states the action and resource, distinguishing it from sibling tools like 'start_torrent' and 'delete_torrent'. However, it lacks nuance about what pausing entails (e.g., stops downloading vs. seeding).

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 on when to use this tool versus alternatives, no prerequisites or conditions mentioned. The description provides no context for optimal usage.

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/philogicae/rqbit-mcp'

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