Skip to main content
Glama
philogicae

rqbit Torrent Client MCP

list_torrents

Get a full list of all torrents currently tracked by the rqbit torrent client, including their names, progress, and status.

Instructions

List all torrents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'list_torrents'. It is registered via @mcp.tool() decorator, calls rqbit_client.list_torrents(), and returns the result as a JSON string.
    @mcp.tool()
    async def list_torrents() -> str:
        """List all torrents."""
        logger.info("Listing all torrents")
        result = await rqbit_client.list_torrents()
        if isinstance(result, str):
            logger.error(f"Error listing torrents: {result}")
            return f"Error listing torrents: {result}"
        return dumps(result)
  • The RqbitClient.list_torrents() method that makes the actual HTTP GET request to /torrents endpoint on the rqbit API server.
    async def list_torrents(self) -> list[dict[str, Any]] | str:
        """list all torrents."""
        return await self._safe_request("GET", "/torrents")  # type: ignore
  • The @mcp.tool() decorator registers list_torrents as an MCP tool with FastMCP.
    @mcp.tool()
  • The tool takes no arguments (no input schema) and returns a string (JSON-encoded list of torrents or error message).
    async def list_torrents() -> str:
Behavior2/5

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

No annotations are provided, and the description only states the action. It lacks disclosure of behavioral traits such as read-only nature, pagination, or authentication requirements. The agent gets minimal behavioral insight.

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?

The description is a single, clear sentence with no waste. It is appropriately sized for a simple tool with no parameters.

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?

Given the tool's simplicity (no parameters, read-like operation) and the presence of an output schema, the description is largely adequate. It could mention the scope of 'all torrents' (e.g., user-level or global) but is otherwise complete.

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

Parameters4/5

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

The input schema has no parameters, so schema description coverage is 100%. The description does not need to add parameter info; it is sufficient for a parameterless tool.

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 'List all torrents' uses a specific verb and resource, clearly distinguishing this tool from siblings like delete, download, or get details. It unambiguously states the operation.

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 such as get_torrent_details or get_torrent_stats. No context about prerequisites or exclusions is given.

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