Skip to main content
Glama
Sign In
mcp-synology

mcp-synology

by cmeans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_download_info

Read-only

Retrieve detailed information for one Synology download task by task_id, including status, destination, transfer statistics, files, trackers, and peers. Use list_downloads first to find the task_id.

Instructions

Get detailed information for a specific download task: detail (status, destination, URI), transfer (size downloaded/uploaded, speed, peers), files (per-file selection for BT), trackers (BT only), peers (BT only). Use list_downloads first to find the task_id. For totals across all tasks, use get_download_stats; for settings, use get_download_config.

Input Schema

NameRequiredDescriptionDefault
task_idYesOne task ID (`dbid_…`), from list_downloads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.1
    • addedInput schema / properties / task_id / description
      Added value: +"One task ID (`dbid_…`), from list_downloads."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "tool_get_download_infoOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.7.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true/destructiveHint=false, so safety is covered. The description adds non-obvious behavioral context: which data blocks are included and the conditional availability of files/trackers/peers (BT only), which prevents an agent from assuming empty results mean failure. It doesn't mention whether trackers/peers can be slow or omitted for non-BT tasks beyond the '(BT only)' note, but that gap is minor.

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?

One dense sentence enumerating return contents, followed by two short routing sentences. Zero filler and front-loaded with the purpose before the sibling disambiguation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates well by listing exactly what the response contains. For a single-parameter read-only lookup with annotations covering the safety profile, nothing an agent needs to call it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100% and the schema already specifies task_id format (`dbid_…`) and its source. The description restates the source ('Use list_downloads first') without adding syntax or validation detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource (retrieve detailed info for a specific download task) and enumerates the four information blocks returned (detail, transfer, files, trackers, peers). Clearly distinguishes itself from get_download_stats and get_download_config by naming both siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing ('Use list_downloads first to find the task_id') plus explicit routing rules for alternatives: totals → get_download_stats, settings → get_download_config. Nothing is left to inference for an agent picking among the three get_* download tools.

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