Skip to main content
Glama
Sign In
mcp-synology

mcp-synology

by cmeans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pause_download

Pauses one or more Synology download tasks by task ID, letting you halt active downloads and manage running tasks through an MCP client.

Instructions

Pause one or more download tasks. When some of the tasks can be paused, an already-paused or finished one is refused for its id (error 405) or shown as not paused: already finished, and the others are paused. When none can be paused (one finished or already-paused task alone, a missing id, or another user's task), the whole call fails with invalid_parameter; list_downloads shows each task's status.

Input Schema

NameRequiredDescriptionDefault
task_idsYesIDs of the tasks to pause, from list_downloads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.1
    • addedInput schema / properties / task_ids / description
      Added value: +"IDs of the tasks to pause, from list_downloads."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "tool_pause_downloadOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.7.1

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description goes far beyond that by disclosing partial-failure semantics, the 405/`not paused: already finished` per-id outcome, and the invalid_parameter whole-call failure conditions. This is exactly the kind of operational detail an agent cannot infer from structured fields.

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?

Front-loaded with the action in the first clause, then failure behavior, with zero filler sentences. The middle sentence is dense and its 'refused for its id (error 405) or shown as...' phrasing is slightly convoluted, but every clause carries information.

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?

With one required parameter and no output schema, the description covers the decisive gaps: which ids fail, what happens on partial success, and where to check status via list_downloads. It does not say what a fully successful call returns, but that is a minor omission for a simple state-change 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%, so the baseline is 3, but the description adds real meaning: a missing id or another user's task causes the entire batch to fail with invalid_parameter rather than being silently skipped. That constraint on the task_ids array is not visible in the schema.

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?

Names a specific verb and resource ("Pause one or more download tasks") and makes the batch scope explicit via "one or more." It is distinct from sibling resume_download by plain naming, but the description never explicitly contrasts the two, which keeps it just short of a 5.

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?

Rather than generic 'when to use' prose, it enumerates the exact states in which the call succeeds, partially succeeds, or fails outright, which tells an agent precisely when invocation is appropriate. It lacks an explicit pointer to resume_download as the inverse operation, so it stops at 4.

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