Skip to main content
Glama
Sign In
transmission-mcp

transmission-mcp

by philogicae
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

add_torrent

Add torrents from magnet links, HTTP URLs, or local file paths to Transmission.

Instructions

Add a torrent from magnet link, HTTP URL, or local file path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "torrent": "<torrent>"
    },
    "name": "add_torrent"
  }
}

Input Schema

NameRequiredDescriptionDefault
pausedNo
torrentYes
download_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0
  2. Removedv1.1.0
  3. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Description lacks behavioral details beyond the basic action. No annotations exist, so the description should disclose side effects, like whether adding a torrent starts downloading immediately (hinted by 'paused' param) or validation behavior for the input types.

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 extraneous words. Efficiently communicates core purpose.

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?

Despite an existing output schema, the description is incomplete for a tool with 3 parameters and no annotations. Fails to explain parameter meanings, return values, or behavioral context like error conditions.

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

Parameters2/5

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

With 0% schema description coverage, the description only partially explains the 'torrent' parameter by listing valid input types. No explanation is given for 'paused' (default false meaning?) or 'download_dir' (null meaning?).

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?

Description explicitly states the tool's function: adding a torrent, and lists three specific sources (magnet link, HTTP URL, local file path). This clearly differentiates it from sibling tools like remove_torrent or pause_torrent.

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 or when to prefer alternatives. Lacks mention of prerequisites, such as whether the torrent URL must be accessible or if the local path must exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools