Skip to main content
Glama
Sign In
mcp-synology

mcp-synology

by cmeans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_file_info

Read-only

Fetch detailed metadata for known file or folder paths—size, owner, timestamps, permissions, and real NAS path—to verify files on Synology volumes.

Instructions

Get detailed metadata for files or folders whose paths you know: size, owner, timestamps, permissions and real path on the volume. To see what's in a folder, use list_files; for a folder's total size, use get_dir_size. A path that doesn't exist is reported as not found.

Input Schema

NameRequiredDescriptionDefault
pathsYesOne or more full paths (`/video/Movies/Dune.mkv`).
additionalNoFields to fetch: `real_path`, `size`, `owner`, `time`, `perm`, `type` (DSM's extension type) and `mount_point_type` (shown only for a mount point). Default: the first five. Unknown values are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.1
    • addedInput schema / properties / additional / description
      Added value: +"Fields to fetch: `real_path`, `size`, `owner`, `time`, `perm`, `type` (DSM's extension type) and `mount_point_type` (shown only for a mount point). Default: the first five. Unknown values are rejected."
    • addedInput schema / properties / paths / description
      Added value: +"One or more full paths (`/video/Movies/Dune.mkv`)."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "tool_get_file_infoOutput",
-  "type": "object"
-}New value: +null
  2. Changed3 schema fields changedv0.7.0
    • addedInput schema / properties / additional
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / paths / title
      Removed value: -"Paths"
    • removedInput schema / title
      Removed value: -"tool_get_file_infoArguments"
  3. First observedv0.4.1

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: the error case for missing paths and a preview of the returned fields. It stops short of saying how multiple paths are handled on partial failure or any batching limits, which keeps it below 5.

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?

Three tight sentences with the core purpose front-loaded, followed by the sibling disambiguation and error behavior. Every sentence carries distinct information.

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?

With no output schema, the description usefully names the returned metadata fields and the not-found behavior, making it callable without opening the schema. It could say a bit more about multi-path results or limits, but nothing critical is missing.

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?

Schema coverage is 100%, so both `paths` and `additional` (field list, defaults, rejected unknown values) are fully documented in the schema. The description only restates example fields like 'real path on the volume' and 'permissions' rather than adding syntax or format details, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — retrieving detailed metadata for files/folders at known paths — and enumerates what metadata (size, owner, timestamps, permissions, real path). It explicitly distinguishes itself from list_files and get_dir_size by naming those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ('whose paths you know') and routes the agent to the correct alternatives: list_files for folder contents and get_dir_size for a folder's total size. It also sets expectations for a non-existent path being reported as not found.

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

Deploy Server

Other Tools