Skip to main content
Glama
synology-mcp
by r03eRt

Drive: starred files

drive_starred
Read-only

List files and folders a user has starred in Synology Drive, with pagination and sorting by name, modified time, size, owner, or type.

Instructions

Files and folders the user marked with a star in Synology Drive.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
sort_byNo
sort_directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

C2.4/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 safety is covered, but the description adds no behavioral context of its own. It says nothing about ordering, pagination defaults, or whether the result set is complete or capped. For a listing tool with four optional controls, that leaves the agent guessing.

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?

It is a single short sentence with zero padding, so nothing is wasted. However, the brevity comes at the cost of under-specification rather than purposeful economy; there is no front-loaded verb or scope statement to anchor it.

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?

With four undocumented parameters, no output schema, and no statement of return shape or ordering, the definition is not complete enough for reliable invocation. The annotations cover the read-only profile, but an agent still cannot tell what a call returns or how paging behaves.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for limit, offset, sort_by and sort_direction, and it mentions none of them. The two enum parameters are partly self-documenting via their allowed values, but limit/offset paging semantics and default sort order are undocumented anywhere.

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 phrase identifies the resource set (starred files and folders in Synology Drive), which hints at a listing operation, but it is a noun fragment with no verb, so the agent must infer that it enumerates rather than retrieves a single item. It distinguishes itself from drive_list only through the word 'starred', with no explicit contrast to siblings like drive_recent or drive_list_labelled.

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 at all: nothing says to pick this over drive_list when the user wants only starred items, nor whether it includes trashed or shared items. The only implied context is the user having marked something with a star.

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