Skip to main content
Glama
synology-mcp
by r03eRt

Drive: shared with me

drive_shared_with_me
Read-only

List files and folders other users shared with you on Synology Drive, with sorting and pagination options.

Instructions

Files and folders other users shared with the logged-in user.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
sort_byNo
sort_directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

C2.8/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. Beyond that the description discloses nothing: no pagination behavior, no default ordering, no indication of whether shared drives or link-shared items are included, and no hint about the shape of returned entries.

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 fragment with no padding, but it is a noun phrase rather than a structured statement of action and behavior, so brevity comes at the cost of under-specification.

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?

For a no-required-parameter list tool this is thin: nothing about default page size, default sort order, whether results are paginated, or what a returned entry contains. Annotations cover the read-only safety profile, but an agent still has to guess at invocation details.

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% across four parameters, so the description carries the full burden of explaining limit, offset, sort_by, and sort_direction, and it says nothing about any of them. The enum values for sort_by and sort_direction are self-explanatory, which keeps this from being a 1, but no added meaning is provided.

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 a specific resource set and, crucially, the direction of sharing ('other users shared with the logged-in user'), which distinguishes it from the sibling drive_shared_with_others without naming it. It never states the verb (list/retrieve), but the resource and scope are unambiguous enough for selection.

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 direction qualifier implicitly signals when this tool is the right one versus 'shared by me', but there is no explicit when-to-use statement, no reference to alternative tools such as drive_search or drive_list, and no guidance on paging through large result sets.

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