Skip to main content
Glama
synology-mcp
by r03eRt

Drive: list folder

drive_list
Read-only

List files and folders in a Synology Drive folder such as My Drive or a team folder, with sorting and pagination for browsing NAS content.

Instructions

List a Synology Drive folder (My Drive or a team folder). Use drive_list_team_folders to find team folders.

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": "drive_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoDrive path: "/mydrive/<path>" (the user's My Drive = /home/Drive in File Station), "/team-folders/<name>/<path>", "id:<file_id>" or "link:<permanent_link>"/mydrive
limitNo
offsetNo
sort_byNo
sort_directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without the description. Beyond naming path families, the description discloses nothing behavioral: no pagination semantics despite limit/offset, no default result ordering, no statement of what an empty or malformed path yields.

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 short sentences, the primary capability front-loaded, and the sibling pointer placed second where it reads as a follow-up. No redundant wording that restates the title or annotations.

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

Completeness2/5

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

Five parameters, 20% schema coverage, and no output schema: the description should carry the paging and ordering story so an agent can list a large folder correctly. It does neither, and with no output schema it also doesn't hint at the shape of the listing returned, leaving the definition thin for a tool that is likely a primary entry point.

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?

Schema description coverage is only 20% — the path property is richly documented while limit, offset, sort_by, and sort_direction carry no descriptions at all. The description compensates only implicitly by naming the path families (My Drive vs team folder) it accepts; it says nothing about paging or sort ordering, so the low-coverage gap is largely unfilled.

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 a Synology Drive folder") and scopes it to My Drive or a team folder, which separates it from browsing-only siblings like drive_list_team_folders. It does not distinguish itself from File Station tools such as list_files or search-oriented siblings like drive_search, so an agent still has to infer that boundary.

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?

It names one concrete alternative with a condition: use drive_list_team_folders to discover team folders before pointing here at a team-folder path. That is useful routing, but there is no when-not guidance relative to the far larger set of siblings (list_files, drive_search, drive_recent, drive_starred), so the guidance is only partially complete.

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