Skip to main content
Glama
synology-mcp
by r03eRt

List shared folders

list_shares
Read-only

Lists Synology NAS shared folders with their free and total storage space, with an option to return only writable shares.

Instructions

List the shared folders (top-level roots such as /photo, /video, /home) with free/total space.

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

Input Schema

NameRequiredDescriptionDefault
only_writableNoOnly list shared folders the user can write to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.6/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 usefully adds the return payload (free/total space per folder), which matters because there is no output schema, but it says nothing about ordering, pagination, or permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the verb and resource, with parenthetical examples that clarify scope without waste. Nothing is extraneous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter read tool with annotations and no output schema, the description covers what it returns (folders plus free/total space) and what the folders are. Minor gaps on ordering and the only_writable filter are tolerable given the annotations and schema coverage.

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?

The single parameter only_writable is fully documented by the schema (100% coverage, including a clear description), so the schema carries this dimension. The tool description never mentions filtering by write access, adding no meaning beyond the schema.

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?

Specific verb+resource: 'List the shared folders' with concrete examples of what a shared folder is (/photo, /video, /home) and an explicit note that free/total space is included. It stops short of distinguishing itself from nearby siblings like drive_list_team_folders or list_files, so an agent must infer the difference from the name.

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?

Usage is only implied: the 'top-level roots' wording suggests this is a broad starting point rather than a deep listing, and the space figures hint at capacity-checking. No explicit when-to-use, when-not-to-use, or named alternative is offered.

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