Skip to main content
Glama
synology-mcp
by r03eRt

Available DSM and package updates

check_updates
Read-only

Checks for available DSM updates and newer versions of installed packages in Package Center without installing them; requires a DSM administrator account.

Instructions

Whether a DSM update is available (version, whether it is a security update and whether it needs a reboot) and which installed packages have a newer version in the Package Center. Only checks; installs nothing. Needs a DSM administrator account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds genuine value by disclosing the result fields (version, security-update status, reboot requirement, package upgrade availability) and the administrator-account requirement. It does not state rate-limit or latency behavior, but for a check-only tool that is a small omission.

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?

A single tightly packed sentence front-loads the primary answer (DSM update availability) before the package-update detail, then closes with the two constraints (no installation, admin account). No filler wording or restatement of the tool name.

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?

There is no output schema, and the description does a fair job of enumerating what comes back, which is the main informational need for a zero-parameter check. The only gap is that the shape of the package list (names plus versions) is implied rather than stated.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the schema is trivially complete. Baseline 4 applies since nothing is left for the description to compensate for.

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?

The description states a specific verb and two concrete resources: it reports whether a DSM update is available and which installed packages have newer versions. Returned details (version, security flag, reboot requirement) make the scope unambiguous, and no sibling tool in the catalog overlaps with this capability.

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?

It clearly frames the tool as read-only reconnaissance ('Only checks; installs nothing'), which tells the agent when this is the right call versus a mutation path. It also states the prerequisite of a DSM administrator account. No explicit alternative sibling is named, but none of the listed siblings performs update checking, so this is a minor gap.

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