Skip to main content
Glama
synology-mcp
by r03eRt

Drive: team folders

drive_list_team_folders
Read-only

Lists Synology Drive team folders the current user can access, so you can identify available shared workspaces before browsing their contents.

Instructions

Team folders the user can access. Browse them with drive_list and path /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_team_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the access-scoping constraint ('the user can access'), which is meaningful behavior. It does not describe what the returned entries contain beyond a name usable in a path, nor ordering or limits.

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 with no filler: the first states the resource, the second states how to act on the results. Front-loaded and appropriately sized for a zero-argument list tool.

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?

With no input parameters, no output schema, and read-only annotations, the definition covers what an agent needs: what is returned (accessible team folders) and how to traverse them. The only minor gap is the exact shape of each returned entry.

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 the baseline is 4 and there is nothing for the description to compensate for. The mention of /team-folders/<name> usefully clarifies that returned names feed into drive_list paths.

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?

The description identifies the resource precisely: team folders the user can access, a distinct scope from sibling listing tools like drive_list_labels or drive_starred. It lacks an explicit verb ('list'), but the resource plus the tool name makes the operation unambiguous.

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

Usage Guidelines4/5

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

It gives concrete follow-up guidance: browse the results with drive_list using path /team-folders/<name>. That is a clear next-step routing instruction. It does not state when this tool should be preferred over other listing tools, but the access-scoped framing implies it.

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