Skip to main content
Glama
Sign In
transmission-mcp

transmission-mcp

by philogicae
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

move_torrent

Move torrent data to a new location by providing the torrent ID and target path.

Instructions

Move torrent data to a new location.

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_id": "<torrent_id>",
      "location": "<location>"
    },
    "name": "move_torrent"
  }
}

Input Schema

NameRequiredDescriptionDefault
moveNo
locationYes
torrent_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'move torrent data to a new location' without specifying if it's a move or copy, what happens to the old location, or any side effects. Minimal behavioral transparency.

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

Conciseness2/5

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

The description is just one sentence, which is concise, but it underspecifies the tool. It lacks necessary details to be useful, thus a 2 for being too sparse.

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?

Given 3 parameters with no descriptions and a file-moving operation, the description is incomplete. While an output schema exists, the description still fails to cover behavioral aspects and parameter context.

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

Parameters1/5

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

Schema description coverage is 0%, so the description should explain parameters. It does not mention the 'move' boolean, 'location' string, or 'torrent_id' at all. The parameter semantics are entirely lacking.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description is clear: 'Move torrent data to a new location.' It states the verb and resource, but doesn't differentiate from siblings like remove_torrent or start_torrent which are clearly different, so a 4 is appropriate.

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 versus alternatives like add_torrent or set_torrent_labels. There's no context about prerequisites or typical scenarios.

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