Skip to main content
Glama
synology-mcp
by r03eRt

List sharing links

list_sharing_links
Read-only

Retrieve the public sharing links you created on a Synology NAS to review, audit, or manage shared files. Use limit and offset to page through results.

Instructions

List the public sharing links created by the 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": "list_sharing_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

C2.9/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 safety and locality are covered structurally. The description contributes the useful scope constraint that only links created by the user are returned, but says nothing about ordering, result volume, pagination behavior, or what a link record contains.

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; the scope qualifier comes early. It is efficient, though its brevity is partly the source of the missing pagination guidance rather than a virtue in itself.

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?

There is no output schema, no parameter documentation, and no pagination or result-shape guidance, so an agent cannot tell how to page through results or what 'the user' means (authenticated caller vs. a target user). For a list tool with two undocumented parameters, the definition leaves too much unstated.

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?

Both parameters (limit, offset) have zero schema description coverage, and the description never mentions pagination, defaults, or maximums. With coverage this low the description is expected to compensate, and it 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 uses a specific verb and resource ('List the public sharing links') and adds a scoping qualifier ('created by the user'). That makes the tool's intent clear, though it never contrasts itself with nearby siblings such as list_shares or drive_list_permissions, leaving overlap ambiguous.

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 statement of when to use this tool versus alternatives, no prerequisites, and no note on when the result set should be filtered elsewhere. An agent must guess whether list_shares or drive_list_permissions is the right call in a given situation.

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