Skip to main content
Glama

NAS connection and server status

nas_status
Read-only

Check NAS reachability, login state, CLI version and allowed access levels. Call it first to diagnose authentication, connection or "not available" errors from other NAS tools.

Instructions

Check whether this server can reach the NAS, and what it is allowed to do. Returns the login state (NAS address and user name, never the token), the unc CLI version, and the server policy: access level, enabled toolsets, allowed NAS paths and whether local file transfer is enabled. Call it first when another tool fails with an authentication, connection or "not available" error. Set doctor to true for a full health report with firmware and component versions and the methods this NAS does not support; that report takes longer, so do not request it before every call.

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

Input Schema

NameRequiredDescriptionDefault
doctorNoAlso run the full health report (firmware, component versions, unsupported methods).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds two useful pieces of behavior beyond that: the token is never returned even though login state is reported, and doctor=true takes longer to run. However, it does not describe error behavior when the NAS is unreachable or any rate/latency limits for the default path.

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?

Three sentences, front-loaded with purpose, then return contents, then when-to-call and the doctor caveat. That order is useful. The middle sentence packs a long comma-separated list of policy fields, but each item maps to a real returned value.

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?

No output schema exists, so the description has to cover return values itself. It does: login state, CLI version, access level, enabled toolsets, allowed paths, local transfer flag, and the extended doctor fields. For a one-optional-flag, read-only tool, an agent has enough to call it correctly and interpret the result.

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. The description adds meaning beyond it: it explains that doctor produces a full health report including firmware, component versions, and unsupported methods, and it adds the cost warning that the report takes longer and should not be requested before every call. That extra cost dimension is real value over the schema.

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 ('Check whether this server can reach the NAS') and then enumerates the returned state: login state, unc CLI version, and server policy (access level, toolsets, allowed paths, local transfer). That is concrete enough to separate it from the file, docker, and system-info siblings without opening any other schema.

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 gives an explicit trigger — 'Call it first when another tool fails with an authentication, connection or "not available" error' — plus a cost-based rule against setting doctor on every call. What it lacks is any statement of when the tool is not worth calling, or a named alternative diagnostic tool, which keeps it at 4 rather than 5.

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