Skip to main content
Glama
synology-mcp
by r03eRt

NAS system info

get_system_info
Read-only

Retrieve basic Synology NAS status, including model, DSM version, RAM, temperature warnings, uptime, clock, and installed packages, without admin rights.

Instructions

Basic NAS status: model, DSM version, RAM, temperature (and whether it is in warning), uptime, NAS clock and which packages used by these tools (Synology Drive, Download Station, Photos) are installed. Works without admin rights.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.8/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 real context beyond that: the auth requirement (no admin rights needed) and the fact that temperature comes with a warning flag, which pre-empts a follow-up call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence carrying the resource and the full field list, followed by the auth caveat. The parenthetical about warning status and the package examples are slightly dense but each earns its place by preventing follow-up calls.

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 must carry the return shape, and it enumerates the fields thoroughly, including which specific packages are checked. Minor gaps remain (units for temperature/RAM, whether uptime is formatted), but an agent can call this confidently.

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 no parameters, so the baseline is 4; there is nothing for the description to disambiguate. The schema is an empty object, consistent with the description's silence on inputs.

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?

"Basic NAS status" plus an explicit enumeration of returned fields (model, DSM version, RAM, temperature, uptime, clock, installed packages) tells an agent precisely what this tool yields. It is clearly distinct in content from siblings like get_system_utilization or get_system_logs, though it never names an alternative to contrast against.

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?

"Basic status" implies a first-look or diagnostic call, and "works without admin rights" gives a usable precondition. However, there is no explicit statement of when to prefer this over get_system_utilization, get_storage_status, or check_updates, so the routing decision is left to inference.

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