Skip to main content
Glama
synology-mcp
by r03eRt

Drive: sharing permissions

drive_list_permissions
Read-only

Lists users and roles with access to a Synology Drive file or folder, helping audit sharing permissions.

Instructions

Who has access to a Drive file or folder and with which role.

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": {
      "path": "<path>"
    },
    "name": "drive_list_permissions"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

C2.8/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 the safe-read profile is established without the description. The description adds only that role information is included in the response, but says nothing about permission inheritance, team-drive vs My Drive differences, or what an empty/denied result looks like.

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

Conciseness3/5

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

One short sentence fragment with no wasted words, and the key concept is front-loaded. However, the brevity comes at the cost of under-specification: it lacks an action verb and reads like a heading rather than an instruction an agent can act on.

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

Completeness3/5

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

For a simple read-only tool with a fully documented single parameter, the description covers the essentials — what is returned and for what resource. With no output schema, though, it should say more about the shape of the result (e.g. list of users/groups with roles) and whether the item must exist.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains the four accepted path forms in detail. The description does not reference the path argument at all, so it adds no meaning beyond the schema — baseline 3 for a fully documented single parameter.

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

Purpose3/5

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

The fragment "Who has access to a Drive file or folder and with which role" does convey the resource (Drive file/folder) and the content of the result (permissions plus role), but it is a noun phrase with no verb and never says "list" or "retrieve." It also draws no boundary against closely related siblings such as list_sharing_links, list_shares, or get_file_info, which an agent could plausibly pick instead.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no exclusions, and no named alternative. The agent is left to infer that this is the permissions view of an item rather than the sharing-link view offered by list_sharing_links or the metadata view of get_file_info.

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