Skip to main content
Glama
synology-mcp
by r03eRt

NAS live resource usage

get_system_utilization
Read-only

Retrieve live CPU, memory, network throughput, and per-disk/per-volume I/O stats from a Synology NAS to monitor system health and diagnose resource usage. Requires DSM administrator access.

Instructions

Live CPU (% and load average), memory (RAM and swap), network throughput and per-disk / per-volume I/O. Needs a DSM administrator account; normal users get an explanatory error.

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_system_utilization"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.9/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 safety is covered. The description adds genuinely non-obvious behavior: a DSM administrator account is required and non-admin callers receive an explanatory error rather than data. It does not discuss polling cost or output shape, but that is a minor gap given the annotation coverage.

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 short sentences with zero filler: the metric list comes first, the access prerequisite second. Every clause carries information an agent would otherwise have to discover by failing a call.

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 parameters and no output schema, the description carries the return-value burden and does so by enumerating the metric families. The auth prerequisite closes the main failure mode. Only a lack of detail on units, sampling window, or response structure keeps it from a 5.

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 nothing to disambiguate; baseline is 4. The description correctly avoids inventing parameter behavior and instead spends its words on what is returned.

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 (subsystem utilization) and enumerates the concrete metrics returned: CPU percentage and load average, RAM/swap, network throughput, and per-disk/per-volume I/O. The word "Live" implicitly separates it from static siblings such as get_system_info, though no sibling is explicitly named.

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 only implied: "Live" signals real-time monitoring rather than historical or configuration queries. There is no explicit statement of when to pick this over get_system_info or get_storage_status, and no exclusions are given.

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