Skip to main content
Glama
philogicae

rqbit Torrent Client MCP

forget_torrent

Remove a torrent from the client without deleting downloaded files. Specify the torrent ID to stop tracking it while preserving data.

Instructions

Forget a torrent, keeping the files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
torrent_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'forget_torrent'. It receives a torrent_id, logs the action, calls the client helper, and returns a success/error message.
    @mcp.tool()
    async def forget_torrent(torrent_id: str) -> str:
        """Forget a torrent, keeping the files."""
        logger.info(f"Forgetting torrent: {torrent_id}")
        result = await rqbit_client.forget_torrent(torrent_id)
        if isinstance(result, str):
            error = f"Error forgetting torrent {torrent_id}: {result}"
            logger.error(error)
            return error
        return "Successfully forgot torrent " + torrent_id
  • The @mcp.tool() decorator that registers 'forget_torrent' as an MCP tool.
    @mcp.tool()
  • The RqbitClient.forget_torrent method that makes the actual HTTP POST request to the rqbit API endpoint /torrents/{id_or_infohash}/forget.
    async def forget_torrent(self, id_or_infohash: str) -> None | str:
        """Forget a torrent, keeping the files."""
        return await self._safe_request("POST", f"/torrents/{id_or_infohash}/forget")
Behavior3/5

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

No annotations provided, so the description must carry full weight. It states the effect on files but does not detail what 'forget' entails (e.g., removal from client, stop seeding, etc.). Adequate but lacks depth for a mutation tool with no annotations.

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?

Single sentence with no extraneous words. Front-loads the action and key information (keeping files). Perfectly concise.

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?

For a simple tool with one parameter and no output schema expectations, the description covers the essential behavior: what it does and what happens to files. It leaves some behavioral details implicit but is largely complete given the tool's simplicity.

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 coverage is 0%, but the description mentions 'torrent' which clarifies that 'torrent_id' is the identifier of the torrent. This adds minimal meaning beyond the schema. A 3 is appropriate given the low coverage and simple context.

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 clearly states the action ('forget') and the resource ('torrent'), and crucially adds 'keeping the files' which distinguishes it from the sibling tool 'delete_torrent'. This makes the purpose highly specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool by contrasting with the likely alternative 'delete_torrent' through the phrase 'keeping the files'. However, it could be more explicit about when to forget versus delete, hence a 4.

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