Skip to main content
Glama
Sign In
mcp-synology

mcp-synology

by cmeans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_download_config

DestructiveIdempotent

Configure Synology Download Station limits and default download destination, updating only supplied fields while enforcing manager-only rate limits and per-user destination settings.

Instructions

Set Download Station global configuration. All parameters are optional: only the fields you pass are updated. The rate fields require a Download Station manager/admin account: DSM silently ignores them from other accounts, so the tool refuses them. Any user can set default_destination: DSM applies it per user, and DS won't start a non-manager's tasks until it is set.

Input Schema

NameRequiredDescriptionDefault
bt_max_uploadNoNAS-wide BitTorrent upload limit in KB/s; `0` means unlimited. Manager/admin accounts only.
bt_max_downloadNoNAS-wide BitTorrent download limit in KB/s; `0` means unlimited. Manager/admin accounts only.
emule_max_uploadNoNAS-wide eMule upload limit in KB/s; `0` means unlimited. Manager/admin accounts only.
emule_max_downloadNoNAS-wide eMule download limit in KB/s; `0` means unlimited. Manager/admin accounts only.
default_destinationNoFolder new tasks go to when create_download gets no destination, share-relative (`video/Torrents`). A non-manager sets only their own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.9.1
    • addedInput schema / properties / bt_max_download / description
      Added value: +"NAS-wide BitTorrent download limit in KB/s; `0` means unlimited. Manager/admin accounts only."
    • addedInput schema / properties / bt_max_upload / description
      Added value: +"NAS-wide BitTorrent upload limit in KB/s; `0` means unlimited. Manager/admin accounts only."
    • addedInput schema / properties / default_destination / description
      Added value: +"Folder new tasks go to when create_download gets no destination, share-relative (`video/Torrents`). A non-manager sets only their own."
    • addedInput schema / properties / emule_max_download / description
      Added value: +"NAS-wide eMule download limit in KB/s; `0` means unlimited. Manager/admin accounts only."
    • addedInput schema / properties / emule_max_upload / description
      Added value: +"NAS-wide eMule upload limit in KB/s; `0` means unlimited. Manager/admin accounts only."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "tool_set_download_configOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.7.1

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: partial-update semantics, admin-only rate fields, DSM silently ignoring them otherwise, the tool refusing them, and the per-user nature of default_destination. This is exactly the context an agent needs to avoid a false success.

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?

Four tight sentences, front-loaded with what the tool does and then the permission caveats. No filler; each sentence carries actionable information.

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?

No output schema exists, but the description covers the critical success/failure semantics for a destructive, idempotent setter: optionality, partial updates, admin-only fields, and per-user defaults. Nothing essential is missing for correct invocation.

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 description coverage is 100%, and each parameter already documents meaning and permissions. The description reinforces the permission model and partial-update behavior, but adds little parameter-level detail beyond 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?

States a specific verb and resource: 'Set Download Station global configuration.' It is immediately distinguishable from read-only siblings like get_download_config, but it does not explicitly name alternatives or sibling boundaries.

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?

Explains that all parameters are optional and only passed fields update, and gives clear permission-based usage rules for rate fields vs. default_destination. It stops short of naming get_download_config or other alternatives explicitly.

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