Skip to main content
Glama

List shared folders

nas_file_roots
Read-only

Lists the shared folders this NAS account can access, providing valid starting paths when a file location is unknown; use the returned paths with other file tools.

Instructions

List the shared folders this NAS account can access. This is the starting point whenever you do not know a path: file access is granted per shared folder, and volume roots such as /volume1 cannot be listed directly. Use the returned paths with the other nas_file_* tools. For the personal folder, call nas_file_list with no path instead.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare this is a safe read (readOnlyHint true, destructiveHint false), so the description adds real behavioral context on top: permissions are granted per shared folder and volume roots cannot be enumerated directly. It does not describe the shape of the returned paths (for example, whether they are absolute or share-relative), which keeps it just below the top score.

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

Conciseness5/5

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

Four short sentences, each doing distinct work: the purpose first, then the when-to-use rule, then the access constraint, then how to consume the result. There is no filler and the most important constraint is front-loaded.

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?

For a parameterless listing tool with no output schema, the description supplies everything an agent needs: when to call it, why it cannot be skipped, and what to do with the paths it returns. The remaining unknown, the exact return format, is minor for a path-list enumeration.

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 zero parameters, so there is nothing to disambiguate and the baseline applies. The description correctly spends its words on routing and constraints rather than inventing parameter detail.

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 states a specific verb and resource ('List the shared folders') and scopes it to what the account can access, which distinguishes it clearly from nas_file_list and the other nas_file_* siblings that operate on paths.

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?

This is explicit routing guidance: it names the situation ('whenever you do not know a path') in which the tool should be used, explains the constraint that makes it necessary (per-shared-folder access, /volume1 cannot be listed), and states the alternative for the personal folder (nas_file_list with no path).

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