Skip to main content
Glama
philogicae

rqbit Torrent Client MCP

get_torrent_details

Fetch detailed information about a specific torrent by its ID or infohash, including metadata and current status.

Instructions

Get details for a specific torrent by its ID or infohash.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
torrent_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool registration via @mcp.tool() decorator — 'get_torrent_details' tool is registered as an MCP tool with input parameter 'torrent_id' (str)
    @mcp.tool()
    async def get_torrent_details(torrent_id: str) -> str:
        """Get details for a specific torrent by its ID or infohash."""
        logger.info(f"Getting details for torrent: {torrent_id}")
        result = await rqbit_client.get_torrent_details(torrent_id)
        if isinstance(result, str):
            error = f"Error getting torrent details {torrent_id}: {result}"
            logger.error(error)
            return error
        return dumps(result)
  • Handler function that calls rqbit_client.get_torrent_details() and returns JSON result or error string
    @mcp.tool()
    async def get_torrent_details(torrent_id: str) -> str:
        """Get details for a specific torrent by its ID or infohash."""
        logger.info(f"Getting details for torrent: {torrent_id}")
        result = await rqbit_client.get_torrent_details(torrent_id)
        if isinstance(result, str):
            error = f"Error getting torrent details {torrent_id}: {result}"
            logger.error(error)
            return error
        return dumps(result)
  • Input schema: single parameter 'torrent_id: str' for the get_torrent_details MCP tool
    async def get_torrent_details(torrent_id: str) -> str:
  • Helper method in RqbitClient class — sends GET request to '/torrents/{id_or_infohash}' via _safe_request, returns dict or error string
    async def get_torrent_details(self, id_or_infohash: str) -> dict[str, Any] | str:
        """Get details for a specific torrent."""
        return await self._safe_request("GET", f"/torrents/{id_or_infohash}")  # type: ignore
  • _safe_request helper — wraps _request with error handling, returns parsed response or error string
    async def _safe_request(self, method: str, path: str, **kwargs) -> Any | str | None:
        try:
            return await self._request(method, path, **kwargs)
        except RqbitHTTPError as e:
            return str(e)
Behavior2/5

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

No annotations provided, so the description carries full burden. It only says 'Get details' without revealing behavioral traits like error handling, rate limits, or whether it returns full details vs a summary. The existence of an output schema mitigates slightly, but transparency is minimal.

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, no wasted words. Conveyed purpose and identifier types efficiently. Appropriate length for a simple retrieval tool.

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?

Given the tool's simplicity and the presence of an output schema, the description is adequate but lacks explicit mention of error or not-found cases. It does not elaborate on what 'details' includes, which could be inferred but not guaranteed.

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?

Schema coverage is 0%, but the description adds that torrent_id can be an ID or infohash, which is not evident from the schema's 'type: string' alone. This adds valuable semantic context beyond the schema.

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 tool retrieves details for a specific torrent, identifying it by ID or infohash. It distinguishes from sibling tools like list_torrents (list all) and delete_torrent (delete).

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 vs alternatives like get_torrent_stats. Usage context is implied but not explicitly stated, leaving the agent without clear selection criteria.

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