Skip to main content
Glama
synology-mcp
by r03eRt

Drive: recent files

drive_recent
Read-only

List files and folders recently used in Synology Drive to find recent work quickly. Set a result limit to control how many recent items are returned.

Instructions

Files and folders the user used recently 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_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 200

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

C2.7/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. The description adds essentially no behavior beyond the name: it never defines the recency window (hours? days?), the ordering of results, or whether filtering by type is possible — the most important behavioral fact for a 'recent' tool is left undefined.

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?

It is one short, front-loaded sentence with no redundant wording or filler. Its brevity reflects under-specification rather than verbosity, and nothing in it needs to be cut.

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-optional-parameter read tool with a full annotation safety profile and no output schema, the definition is minimally adequate. The notable gap is the undefined recency window and result ordering, which an agent needs in order to describe results to a user.

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?

Schema coverage is 100% and there is a single optional 'limit' parameter fully documented in the schema with its default of 200. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 description names a concrete resource ('files and folders the user used recently in Synology Drive'), which tells an agent what data comes back, but it is a bare noun phrase with no verb and no differentiation from siblings like drive_starred, list_files, or drive_search, which all return file listings.

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 and no mention of alternatives. An agent cannot tell from this text whether to pick this over list_files, drive_starred, or drive_search when a user asks for 'my files', leaving the choice to inference.

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