mcp-synology

Overview Schema Source Related Servers Discussions Admin

search_files

Read-only

Find files on your Synology NAS by keyword, extension, size, or modification date. Filters filenames and metadata recursively to locate files across folders.

Instructions

Search recursively for files by keyword, extension, size, or modification date. The pattern parameter is a keyword/substring match on filenames (not glob). Use extension for file type filtering (e.g., extension="mkv"). Accepts human-readable sizes like "500MiB". mtime_from / mtime_to accept ISO 8601 ("2026-04-01T12:00:00+00:00"), a calendar date ("YYYY-MM-DD"), or Unix epoch seconds; naive dates are treated as UTC. For directory contents or sizes, use list_files or get_dir_size instead.

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`pattern`	No
`size_to`	No
`filetype`	No	all
`mtime_to`	No
`extension`	No
`recursive`	No
`size_from`	No
`mtime_from`	No
`folder_path`	Yes
`exclude_pattern`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.8.0Oct 17, 2026
- removedInput schema / properties / additional
```
Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
```
Changed28 schema fields changedv0.7.0Oct 15, 2026
- addedInput schema / properties / additional
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- removedInput schema / properties / exclude_pattern / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / exclude_pattern / default
```
Removed value: -null
```
- removedInput schema / properties / exclude_pattern / title
```
Removed value: -"Exclude Pattern"
```
- addedInput schema / properties / exclude_pattern / type
```
Added value: +"string"
```
- removedInput schema / properties / extension / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / extension / default
```
Removed value: -null
```
- removedInput schema / properties / extension / title
```
Removed value: -"Extension"
```
- addedInput schema / properties / extension / type
```
Added value: +"string"
```
- removedInput schema / properties / filetype / title
```
Removed value: -"Filetype"
```
- removedInput schema / properties / folder_path / title
```
Removed value: -"Folder Path"
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- addedInput schema / properties / mtime_from
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / mtime_to
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / pattern / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / pattern / default
```
Removed value: -null
```
- removedInput schema / properties / pattern / title
```
Removed value: -"Pattern"
```
- addedInput schema / properties / pattern / type
```
Added value: +"string"
```
- removedInput schema / properties / recursive / title
```
Removed value: -"Recursive"
```
- removedInput schema / properties / size_from / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / size_from / default
```
Removed value: -null
```
- removedInput schema / properties / size_from / title
```
Removed value: -"Size From"
```
- addedInput schema / properties / size_from / type
```
Added value: +"string"
```
- removedInput schema / properties / size_to / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / size_to / default
```
Removed value: -null
```
- removedInput schema / properties / size_to / title
```
Removed value: -"Size To"
```
- addedInput schema / properties / size_to / type
```
Added value: +"string"
```
- removedInput schema / title
```
Removed value: -"tool_search_filesArguments"
```
First observedv0.4.1Apr 8, 2026

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 genuinely useful behavior beyond annotations: pattern is a substring match not a glob, dates are normalized to UTC, and recursion is inherent. It does not cover result ordering, pagination, or limit behavior, so it falls short of a 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?

Front-loaded with purpose, then format semantics, then alternative routing. Every sentence carries distinct, non-redundant information with no filler.

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?

An output schema exists, so return values need not be explained, and the safety profile comes from annotations. For an 11-parameter tool with zero schema descriptions, the description supplies the critical format semantics but leaves limit, filetype, and exclude_pattern undocumented, making it strong but not fully complete.

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 description coverage is 0%, so the description carries the full parameter burden and does well for pattern, extension, size_from/to, and mtime_from/to by giving formats and examples. However, several parameters that affect correct invocation are never mentioned: limit, filetype, recursive, exclude_pattern, and folder_path. Partial coverage keeps this at a 3.

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 ('Search recursively for files') plus the exact facets it searches by (keyword, extension, size, modification date). It also names the sibling tools it is not (list_files, get_dir_size) for the directory-contents/sizes case, so an agent can route correctly without opening schemas.

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?

Explicitly provides when-not-to-use guidance: 'For directory contents or sizes, use list_files or get_dir_size instead.' This is a clear alternative-routing instruction, not mere implied context.

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