Skip to main content
Glama
synology-mcp
by r03eRt

Drive: files with a label

drive_list_labelled
Read-only

Retrieves Synology Drive files and folders that carry a specified label ID, so you can locate and organize labeled NAS content.

Instructions

Files and folders that carry a given label (label_id from drive_list_labels).

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": {
      "label_id": "<label_id>"
    },
    "name": "drive_list_labelled"
  }
}

Input Schema

NameRequiredDescriptionDefault
label_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.5/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 without prose. The description adds only the modest content fact that results include both files and folders; it says nothing about pagination, result limits, ordering, or whether nested folder contents are included.

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

Conciseness4/5

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

A single short sentence with zero filler, and the key scoping information comes first. It reads as a fragment, which keeps it compact but leaves the listing action implicit.

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 one-parameter read-only lookup with no output schema and annotation coverage of the safety profile, the definition is serviceable but thin. An agent still cannot tell whether results are paginated or truncated, which matters for a list-shaped tool.

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 0%, so the description carries the burden, and it does partially: it establishes that the parameter is an identifier rather than a display name and points to drive_list_labels as the source. It still does not state the expected ID format or whether multiple labels can be combined.

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 names the resource precisely (files and folders carrying a given label) and scopes it to a single label, which separates it from the sibling drive_list_labels that enumerates labels themselves. It is a noun phrase rather than a verb+resource statement, so the listing action is only implied by the tool name.

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 parenthetical '(label_id from drive_list_labels)' gives an explicit prerequisite and a chaining cue to the sibling that supplies the argument. There is no statement of when to prefer this over list_files or drive_search, nor any exclusion for unlabelled queries.

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