Skip to main content
Glama
synology-mcp
by r03eRt

NAS storage health

get_storage_status
Read-only

Checks Synology NAS storage health by retrieving RAID pool status, volume capacity and warnings, and internal disk temperature, SMART status, and bad sectors.

Instructions

Storage pools (RAID type, status, member disks), volumes (filesystem, used/free space, status and warnings such as fs_almost_full) and internal disks (model, size, temperature, SMART status, bad sectors). Serial numbers are not returned. 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": "get_storage_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: a DSM administrator account is required, and serial numbers are deliberately excluded from the response, which saves the agent from chasing data that will never appear.

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?

Roughly three compact clauses: what is returned grouped by pool/volume/disk, a data exclusion, and an auth prerequisite. It is front-loaded, contains no filler, and every sentence earns its place.

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 no output schema, the description carries the burden of describing the return shape, and it does so thoroughly at the field level, including warning states like fs_almost_full. Only the nesting/format of the response (single object vs. list per category) is left implicit, a minor gap for a read-only status 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?

With zero parameters the baseline is 4; there is nothing for the description to disambiguate, and it correctly implies a no-argument, whole-system query. No syntax or format details are needed.

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?

The description names the resource (storage pools, volumes, internal disks) and enumerates the concrete fields returned (RAID type, filesystem, SMART status), so an agent knows exactly what data this tool surfaces. It falls short of 5 because it never states a verb-driven purpose or distinguishes itself from the sibling get_disk_health, which plausibly overlaps.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named despite get_disk_health and get_system_info being adjacent concerns. The agent must infer from content that this is the broad storage-health call.

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