Skip to main content
Glama
synology-mcp
by r03eRt

Drive: shared with others

drive_shared_with_others
Read-only

Lists files and folders in My Drive or team folders that you have shared with other people, with sorting and pagination options.

Instructions

Files and folders of the user (My Drive or team folders) that are shared with other people.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
sort_byNo
sort_directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

B3/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 useful scope detail — that both My Drive and team folders are included and that the criterion is outgoing shares — but says nothing about pagination defaults, result ordering, or whether inherited/domain-wide shares count.

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 front-loaded sentence with no filler or redundancy. It is efficient, though efficiency here comes partly from leaving important behavior unstated rather than from tight editing.

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?

The tool is simple, read-only, and has no output schema, and the description does convey the item set returned. What is missing is pagination and sorting behavior for a list tool with 4 unannotated parameters, which leaves an agent guessing at defaults and result caps.

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 (limit, offset, sort_by, sort_direction), and the description supplies no semantics for any of them — no default page size, no default sort order. With the schema providing only types and enums, the description needed to compensate and does not.

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 and scope: files and folders in the user's My Drive or team folders that are shared with other people. That scope implicitly separates it from the sibling drive_shared_with_me, though the verb (list/retrieve) is never stated explicitly and no sibling is named.

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 explicit when-to-use guidance, no exclusions, and no mention of an alternative such as drive_shared_with_me, drive_list, or drive_search. The scope sentence implies the domain, but an agent must infer the routing decision entirely.

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