Skip to main content
Glama
synology-mcp
by r03eRt

Folder size

get_dir_size
Read-only

Calculates total size, file count, and folder count for one or more paths on a Synology NAS, helping you audit storage usage before organizing files.

Instructions

Calculate total size, number of files and number of folders for one or more paths.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paths": "<paths>"
    },
    "name": "get_dir_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

B3.4/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 return-shape information (three aggregate metrics), but never discloses that this is a recursive scan that may be slow or expensive on deep trees, nor how errors on individual paths are handled.

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, and every clause (total size, file count, folder count, multiple paths) carries information. Nothing is padded or repeated from the schema.

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 simple read-only aggregation tool with annotations and only one parameter, the description is serviceable but stops short. It leaves open the recursive-scan cost and the behavior for inaccessible or nonexistent paths, which matter when a caller passes several paths.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single schema property carries only a regex pattern, so the description must compensate. It does explain that multiple paths are accepted and that results are aggregated across them, which is meaningful beyond the raw schema, though it omits whether paths must be absolute.

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?

States a specific verb (calculate) plus the exact outputs: total size, file count, and folder count, for one or more paths. This distinguishes it from list_files or get_file_info at a glance, though it does not name or explicitly contrast any sibling.

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, no mention of an alternative like get_file_info for single-file details, and no statement of when not to use it. Usage can only be inferred from the tool name and the word 'paths'.

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