Skip to main content
Glama

System version and hardware settings

nas_system_info
Read-only

Read a group of UGREEN NAS system settings such as identity, update status, fan, beep, CPU, LED, ZRAM, power, and UPS to inspect current configuration without making changes.

Instructions

Read one group of system settings. "identity": device model and system version. "update_status": whether a system update exists (read-only; it never starts a check or an update, and UNSPECIFIED means unknown, not up to date). "fan", "beep", "cpu", "led", "zram", "power" and "ups": the corresponding control panel settings. For cpu, when is_support says frequency control is unsupported, the frequency value is meaningless. For ups, read right_now first (true means act immediately); otherwise a standby_time of "-1" means "when the UPS battery is low", not "unset". "identity", "update_status" and "zram" are missing on older control panel versions and then report "not available"; do not retry, and use nas_status with doctor: true for the firmware version instead. Nothing here can be changed through this server.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "nas_system_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhich settings to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces that with 'Nothing here can be changed through this server.' Beyond that it discloses that update_status never triggers a check or update, that UNSPECIFIED means unknown rather than current, that certain kinds are absent on older control panel versions, and that retrying is futile — all behavior an agent could not infer from annotations alone.

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?

The scoping statement and the update_status caveat are front-loaded, and nearly every clause carries a distinct rule. It is dense and quote-heavy in the middle, which costs a little readability, but no sentence is filler.

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?

There is no output schema, so the description has to convey what comes back, and it does so per kind plus the fallback 'not available' behavior and the correct alternative for firmware version. For a read-only selector tool with one enum parameter, nothing an agent needs to call and interpret it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the single parameter has 100% schema coverage, the description adds real meaning to each enum value by explaining what that group represents and its interpretation rules. The cpu is_support caveat and the ups right_now/standby_time semantics ('-1' means 'when the UPS battery is low', not 'unset') are exactly the kind of value-level meaning the schema cannot carry.

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 opens with a specific verb and resource ('Read one group of system settings') and then enumerates all nine selectable groups, so an agent knows exactly what the tool returns. It also names a concrete sibling, nas_status with doctor: true, for the one thing this tool cannot supply (firmware version), which separates it from the rest of the nas_* family.

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?

Guidance is explicit for the tricky cases: read ups right_now first, do not retry kinds that report 'not available', and use nas_status with doctor: true instead for firmware version. It does not broadly state when to prefer this tool over nas_network_info or nas_storage_info for overlapping settings, so routing guidance is strong but not exhaustive.

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