Skip to main content
Glama
synology-mcp
by r03eRt

List folder contents

list_files
Read-only

Browse files and folders in a Synology NAS directory with paging, sorting, glob pattern matching, and file-type filters to find or inspect stored content.

Instructions

List files and folders inside a NAS folder. Supports paging, sorting, glob filtering and file type filtering.

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": {
      "folder_path": "<folder_path>"
    },
    "name": "list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return (default 200, 0 = all)
offsetNo
patternNoGlob filter on names, e.g. *.pdf. Without * or ? it matches partially. Comma separates patterns.
sort_byNo
filetypeNoOnly files, only folders, or both (default all)
folder_pathYesFolder to list, starting with a shared folder, e.g. /photo/2024
sort_directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe, non-open-world listing operation. The description usefully adds paging, sorting, glob filtering, and file type filtering, but it does not disclose recursion behavior, default ordering, or other operational details beyond the annotations.

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?

Two tight sentences, front-loaded with the core action and followed by supported capabilities. Every phrase earns its place and there is no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter, read-only listing tool with annotations and no output schema, the definition covers the purpose and main capabilities. Minor gaps remain around recursion, return shape, and default behavior, but the schema carries most parameter semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description maps its capability phrases to paging, sorting, glob filtering, and file type filtering, which correspond to several parameters. With 57% schema description coverage, it offers some conceptual compensation, but it does not add parameter details beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: list files and folders inside a NAS folder. The folder scope helps distinguish it from search-oriented siblings, though it does not explicitly name an alternative such as search_files.

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

Usage Guidelines3/5

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

The intended use is implied by 'inside a NAS folder', and the supported operations are mentioned. However, there is no explicit guidance on when to use this instead of search_files or drive_list, nor any exclusion conditions.

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