Skip to main content
Glama

Network interfaces and general network settings

nas_network_info
Read-only

Retrieve UGREEN NAS network details: list interfaces with link state, speed, MAC and IPv4/IPv6 settings, or return default gateway, DNS mode and proxy configuration.

Instructions

kind "interfaces" (default) lists network interfaces (data.ifaces[]) with link state, speed, MAC and IPv4/IPv6 settings; pass iface to see only one. To find the NAS address, take an interface whose connection is CONNECT_STATUS_CONNECTED and whose ipv4.ip_addr is not empty: decide by ip_addr, not by ipv4.status, which reads "enabled" even without an address. A speed of -1 or 0 means no link. An unknown interface name returns an empty list rather than an error. kind "general" returns the default gateway, DNS mode and servers, and proxy settings; the manual DNS list there only applies in manual mode and may differ from the per-interface DNS, so report both when asked about DNS. Network settings cannot be changed through this server.

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

Input Schema

NameRequiredDescriptionDefault
kindNoInterfaces, or gateway/DNS/proxy.interfaces
ifaceNo"interfaces" only: one interface name, for example eth0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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, yet the description adds substantial behavioral detail beyond them: an unknown interface name returns an empty list instead of an error, speed of -1 or 0 means no link, and ipv4.status reads "enabled" even without an address so ip_addr is the reliable signal. These are exactly the non-obvious traps an agent needs to interpret results correctly.

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?

Content is front-loaded with the default behavior first, then the per-mode details and finally the read-only constraint. Sentences are dense and semicolon-packed, so it is slightly heavy to scan, but essentially every clause carries actionable information.

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, the description carries the full burden of describing return values and does so: data.ifaces[] with link state, speed, MAC and IP settings for the default mode, and gateway/DNS/proxy for "general", including the caveat that manual DNS may differ from per-interface DNS and both should be reported. Nothing needed to call or interpret the tool is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: iface restricts output to a single interface and an unrecognized name yields an empty list rather than a failure, and kind's default is restated behaviorally. That extra guidance on how to choose between the enum values justifies a 4.

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 names the two operations precisely by enum value: kind "interfaces" lists network interfaces with link state, speed, MAC and IPv4/IPv6 settings, while kind "general" returns gateway, DNS mode/servers and proxy settings. An agent can tell immediately that this is a read-only network-inventory tool and what data comes back for each mode.

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?

It explicitly documents the default (kind "interfaces"), when to pass iface to narrow to one interface, and when to switch to kind "general" for gateway/DNS/proxy. It also sets a firm boundary that network settings cannot be changed through this server, steering an agent away from expecting mutation. It stops short of naming sibling tools for adjacent queries (e.g. system or status info), so a 4 rather than a 5.

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