Skip to main content
Glama
Sign In
ugreen-nas-mcp

ugreen-nas-mcp

by Mrgaols
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Disk usage and folder quota

nas_file_usage
Read-only

Measure folder space usage with optional depth breakdown, or check quota limits for personal and shared NAS folders.

Instructions

kind "du" reports how much space folders occupy (items[].entries[] with size, dir_count and file_count), optionally broken down to a given depth; it walks the tree and can be slow. kind "quota" reports the size limit set on a personal or shared folder: the value is in MB as a string, and "0" means no quota is set, not a quota of zero. Quotas exist only at the level of a personal or shared folder, not on subfolders or volume roots. For free space on a whole volume use nas_storage_info with kind "volumes".

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>",
      "paths": "<paths>"
    },
    "name": "nas_file_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes"du" for space used, "quota" for the configured limit.
depthNoFor "du" only: break usage down this many levels deep.
pathsYesFolders to measure. Absolute NAS paths (1 to 20).
timeout_secondsNoTime limit in seconds (default 120, max 1800). Raise it for large folders or files; a result cut off by the limit is incomplete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered; the description goes further by disclosing that du walks the tree and can be slow, that a result cut off by timeout_seconds is incomplete, and that quota "0" means no quota rather than zero. Those are exactly the behavioral traps an agent would otherwise fall into.

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?

Dense and mostly front-loaded, leading with the du mode and its return shape before moving to quota and the volume alternative. No sentence is filler, though the run-on parenthetical about items[].entries[] makes it slightly harder to scan than it needs to be.

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 carries the return-shape burden and does so by naming items[].entries[] fields for du and the string-MB/zero convention for quota. Combined with the timeout and scope rules, an agent has everything needed to call this correctly on the first try.

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 semantics the schema lacks: quota values are in MB as a string, "0" means unset, depth applies to du only, and timeout truncation yields incomplete results. The only remaining gap is that absolute path format expectations are left to 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?

Names both modes concretely: kind "du" reports folder space consumption with the exact response fields (items[].entries[] with size, dir_count, file_count), and kind "quota" reports the configured size limit on a personal or shared folder. It also explicitly routes volume-level free-space questions to the sibling nas_storage_info, so an agent can separate this tool from its neighbors without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance per mode plus a hard exclusion: quotas exist only at the personal or shared folder level, not on subfolders or volume roots, and whole-volume free space belongs to nas_storage_info with kind "volumes". The performance caveat (tree walk, can be slow, raise timeout) further tells the agent when this call is expensive versus cheap.

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

Deploy Server

Other Tools