Skip to main content
Glama
synology-mcp
by r03eRt

Get file info

get_file_info
Read-only

Retrieve size, timestamps, owner, and real volume path details for one or more files or folders on a Synology NAS to verify file metadata.

Instructions

Get details (size, dates, owner, real path on the volume) for one or more files/folders.

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

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 genuinely useful behavior beyond that: it accepts multiple paths in one call and returns the resolved 'real path on the volume' rather than the logical path. It does not say what happens for missing/inaccessible paths or whether folders are traversed.

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 front-loaded sentence with the resource first and the concrete payload fields parenthesized. Every phrase earns its place and nothing is padding.

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 simple read-only lookup with no output schema, listing the returned fields and the batch capability is most of what an agent needs. Gaps remain around folder-vs-file behavior and error handling, but these are minor relative to the tool's complexity.

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?

With a single parameter and 0% schema description coverage, the description carries the burden, and it does clarify that multiple paths are accepted per call. However, it omits the absolute-path requirement encoded in the schema pattern (^\/.*), so an agent could still pass relative paths incorrectly.

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 gives a specific verb ("Get details") and resource (files/folders) and even enumerates the returned fields: size, dates, owner, real path on the volume. It is clear what the tool does, but it never distinguishes itself from plausible siblings such as get_dir_size, list_files, or drive_get_info.

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 guidance on when to choose this over the many list/info siblings, no prerequisites, and no conditions for exclusion. The only implicit hint is that it takes known paths ("one or more files/folders"), which tells the agent nothing about alternatives.

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