Skip to main content
Glama
synology-mcp
by r03eRt

Disk health (SMART)

get_disk_health
Read-only

Retrieve per-disk health from Synology Storage Manager, including status, SMART results, bad sectors, power-on hours, remaining life, and temperature; check all disks or one specified disk.

Instructions

Per-disk health from Storage Manager: overall status, SMART status and last test, bad sectors (and whether they are growing), power-on hours, remaining life, temperature and the SMART attributes that matter (or all of them). Needs a DSM administrator account. Serial numbers are never returned.

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": "get_disk_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
diskNoOnly this disk: its id ("sda") or name ("Drive 1"). Default: all disks
all_attributesNoReturn every SMART attribute instead of only failing and key ones (bad sectors, temperature, power-on)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the supplied readOnly/openWorld annotations: it discloses a privilege requirement ('Needs a DSM administrator account') and a data-exposure limit ('Serial numbers are never returned'), both of which an agent must know before planning a call. It also flags that bad-sector growth is reported, which signals a trend-oriented output rather than a snapshot.

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?

Two sentences, front-loaded with the resource and scope, then the returned fields, then the access/limitation notes. No filler, and the most decision-relevant facts (admin requirement, no serial numbers) are placed where they will be read.

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 and only read-only annotations, the description carries the burden well: it covers what is returned, the mode switch on attribute verbosity, the privilege precondition, and a privacy constraint. Nothing an agent needs to select or invoke this tool 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%, so both parameters are already fully documented in the schema, including the default-to-all-disks behavior and the meaning of all_attributes. The clause 'the SMART attributes that matter (or all of them)' mirrors rather than extends the schema, so the baseline 3 applies.

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 ('per-disk health from Storage Manager') and then enumerates the exact data returned (SMART status, last test, bad sectors and growth, power-on hours, remaining life, temperature). The per-disk scope plus SMART-attribute detail clearly separates it from volume/system-level siblings such as get_storage_status or get_system_info.

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

Usage Guidelines3/5

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

Usage is implied by the field list and the note that an administrator account is required, but there is no explicit when-to-use guidance or routing to/away from alternatives (e.g. storage-status vs disk-health). It also doesn't say when the 'all disks' default is preferable to targeting one disk.

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