Skip to main content
Glama

List a folder

nas_file_list
Read-only

Lists entries in a NAS folder, defaulting to the logged-in user's personal folder, so you can browse shared-directory contents and optionally recurse into subfolders.

Instructions

List the entries of a folder on the NAS. Omit path to list the personal folder of the logged-in user. Volume roots such as /volume1 are not accessible; start from a shared folder (see nas_file_roots). Entries are in items[0].entries[]; size and the time fields are strings holding 64-bit integers, and the mode field is unreliable, so do not use it to judge permissions. Recursive listing of a large folder can take a minute or more: prefer a deeper path, or nas_search_files when looking for a file by name.

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

Input Schema

NameRequiredDescriptionDefault
pathNoFolder to list. Absolute NAS path, for example /volume1/docs/report.pdf.
limitNoMaximum number of entries; 0 means no limit.
recursiveNoAlso list all subfolders. Slow on large folders.
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.9/5.0
Behavior5/5

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

Goes well beyond the readOnly/non-destructive annotations by disclosing the result shape (items[0].entries[]), the string-encoded 64-bit size and time fields, and the warning that mode is unreliable for permission judgments. It also flags the performance trait that recursive listing of a large folder can take a minute or more.

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 tight sentences, front-loaded with what the tool does, followed by access constraints, result shape, and performance alternatives. Each sentence carries distinct operational information with no 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?

With no output schema, the description compensates by describing the entries location and field typing caveats. Access limits, default-path behavior, and slowness handling cover everything needed to invoke this correctly; the only residual confusion comes from the input schema's /volume1 example, which the description correctly overrides.

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 already 100%, so the baseline is 3, but the description adds real meaning: omitting path targets the logged-in user's personal folder, and recursive is framed as the slow option to avoid in favor of a deeper path. The timeout wording largely restates the schema's 'result cut off by the limit is incomplete' note, so it is not perfect.

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?

States a specific verb and resource ('List the entries of a folder on the NAS') and explicitly differentiates itself from nas_search_files for name-based lookup and from nas_file_roots for entry points. The default behavior when path is omitted is spelled out, so the agent knows exactly what the call produces.

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 concrete when-to-use rules: omit path for the personal folder, avoid /volume1 roots and start from a shared folder via nas_file_roots, prefer a deeper path over recursive listing, and use nas_search_files when hunting a file by name. It also states an exclusion (volume roots not accessible), which is exactly the kind of guidance that prevents failed calls.

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