Skip to main content
Glama
synology-mcp
by r03eRt

Drive: list labels

drive_list_labels
Read-only

List Synology Drive labels with their IDs and colors so you can identify and apply the correct label when organizing files.

Instructions

The user's Synology Drive labels with their IDs and colors.

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_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

B3.4/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 safety profile is covered. The description adds genuine value beyond that by disclosing the return contents (label IDs and colors), which matters since no output schema exists. It stops short of saying whether results are scoped to the authenticated user or whether pagination applies.

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?

One short fragment with zero padding, and the key payload facts are stated immediately. It is under-specified rather than bloated, and could be made a complete sentence without added length.

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 no-parameter, read-only listing tool with no output schema, stating the returned resource and its fields is close to sufficient. Only the scope (current user's labels) and the absence of filtering/pagination caveats are left implicit.

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, which is the baseline-4 case. The description's statement about returned IDs and colors is the only parameter-adjacent detail possible here, and nothing is missing.

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 (the user's Synology Drive labels) and the payload fields (IDs and colors), so an agent knows what it gets back. It is a noun phrase rather than a verb+resource statement, so the 'list' action comes largely from the name and title, and it does not distinguish itself from the adjacent `drive_list_labelled` sibling.

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 guidance, no mention of prerequisites, and no reference to any alternative tool such as `drive_list_labelled` or `drive_list`. The agent must infer the call context entirely from the name.

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