Skip to main content
Glama
philogicae

rqbit Torrent Client MCP

start_torrent

Resume a paused or stopped torrent by specifying its unique torrent ID.

Instructions

Start (resume) a torrent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
torrent_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler function for 'start_torrent'. Decorated with @mcp.tool(), it takes a torrent_id parameter, calls the client's start_torrent method, and returns a success or error string.
    @mcp.tool()
    async def start_torrent(torrent_id: str) -> str:
        """Start (resume) a torrent."""
        logger.info(f"Starting torrent: {torrent_id}")
        result = await rqbit_client.start_torrent(torrent_id)
        if isinstance(result, str):
            error = f"Error starting torrent {torrent_id}: {result}"
            logger.error(error)
            return error
        return "Successfully started torrent " + torrent_id
  • The RqbitClient wrapper method that executes the actual HTTP API call. Sends a POST request to /torrents/{id_or_infohash}/start to resume the torrent.
    async def start_torrent(self, id_or_infohash: str) -> None | str:
        """Start (resume) a torrent."""
        return await self._safe_request("POST", f"/torrents/{id_or_infohash}/start")
  • The @mcp.tool() decorator on line 78 registers 'start_torrent' as an MCP tool. The tool name is derived from the function name 'start_torrent'.
    @mcp.tool()
  • The function signature for start_torrent defines the input schema: takes a string parameter 'torrent_id' and returns a string.
    async def start_torrent(torrent_id: str) -> str:
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral traits. It only states 'Start (resume) a torrent' without disclosing side effects (e.g., if already running, whether it resets progress, or auth requirements). This is insufficient for a mutation tool.

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

Conciseness2/5

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

The description is extremely short (three words), which sacrifices informativeness for brevity. It lacks structure or any supplementary details that would aid an agent in invoking the tool correctly. Conciseness is not an asset when it omits critical information.

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?

With one parameter and an output schema (content unknown), the description is too vague. It does not specify behavior when the torrent is already running, what constitutes success, or error conditions. Sibling tools provide context but the description fails to leverage or clarify its role.

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

Parameters1/5

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

Schema description coverage is 0% for the only parameter 'torrent_id', and the description adds no explanation of what the ID represents, how to obtain it, or expected format. The description adds zero semantic value beyond the schema's type definition.

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 action 'Start (resume)' on the resource 'torrent', which is a specific verb+resource combination. It distinguishes from siblings like 'pause_torrent' (opposite) and 'delete_torrent' (destructive), but lacks any elaboration on scope or state.

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. The siblings include 'pause_torrent' and 'download_torrent', but the description does not clarify that it is intended for resuming a paused torrent or starting a newly added one. No exclusion criteria or contextual cues provided.

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