Skip to main content
Glama
montyanderson

transmission-mcp

Get Torrent Details

transmission_get_torrent
Read-onlyIdempotent

Retrieve detailed information about one or more torrents by ID, including status, progress, files, trackers, and peer connections.

Instructions

Get detailed information about specific torrent(s) by ID.

This tool retrieves comprehensive information about one or more torrents, including status, progress, files, trackers, and peer information.

Args:

  • ids (number | number[] | 'all'): Torrent ID(s) - single ID, array of IDs, or 'all' for all torrents

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Detailed torrent information including:

  • Name, status, and progress

  • Size and download/upload statistics

  • Speed and ETA

  • Peer connections

  • Labels and error messages (if any)

Examples:

  • Use when: "Show me details for torrent ID 5" -> params with ids=5

  • Use when: "Get info for torrents 1, 2, and 3" -> params with ids=[1, 2, 3]

  • Use when: "Show all torrent details" -> params with ids='all'

Error Handling:

  • Returns "No torrents found matching the specified IDs" if IDs don't exist

  • Returns error message if connection fails

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesTorrent ID(s) to operate on - can be a single ID, array of IDs, or 'all'
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by detailing return information, error messages, and connection failure scenarios, which goes beyond the annotations.

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

Conciseness4/5

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

The description is structured with clear sections (Args, Returns, Examples, Error Handling) and is front-loaded with the purpose. Slightly wordy in examples but overall efficient.

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 no output schema, the description provides a return summary covering all key fields. It explains parameters, error handling, and usage examples, leaving no critical gaps for a read-only tool.

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 100%, baseline 3. The description adds examples and explains parameter types and default values, improving meaning beyond the schema alone.

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 'Get detailed information about specific torrent(s) by ID,' using a specific verb and resource. It distinguishes itself from sibling tools like transmission_list_torrents by focusing on detailed info for specific IDs rather than a list.

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 provides concrete examples of when to use the tool (e.g., 'Show me details for torrent ID 5') and includes error handling. However, it does not explicitly state when not to use or compare with siblings, so it is slightly incomplete.

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/montyanderson/transmission-mcp'

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