Skip to main content
Glama
synology-mcp
by r03eRt

Search files

search_files
Read-only

Search files and folders across specified Synology NAS folders recursively by name pattern, extension, size, date, or owner and return matching results.

Instructions

Search recursively for files/folders by name pattern, extension, size, date or owner. Waits for the search to finish (up to the task timeout) and returns matches.

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": {
      "folder_paths": "<folder_paths>"
    },
    "name": "search_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (default 200)
ownerNo
patternNoGlob on name, e.g. *invoice*. Without * or ? it matches partially.
size_toNoMax size in bytes
filetypeNo
extensionNoExtension glob, e.g. pdf or jpg,png
recursiveNoSearch subfolders too (default true)
size_fromNoMin size in bytes
folder_pathsYesFolders to search in, e.g. ["/photo"]
modified_afterNoISO date, e.g. 2024-01-01
modified_beforeNoISO date

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: the call is synchronous and blocks until the search completes or the task timeout is hit. It doesn't mention rate limits or pagination, so it is strong but not exhaustive.

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

Conciseness4/5

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

Two compact sentences with zero filler, front-loaded with the action and criteria, then the blocking behavior. Nothing is redundant, though the second sentence could be folded in more gracefully.

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 an 11-parameter search with no output schema, the description covers the action, criteria and blocking behavior, but says only 'returns matches' without indicating result shape, ordering, or what happens on timeout truncation. Adequate but with clear gaps.

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 82%, so the schema already documents glob syntax, size bounds, date formats and defaults. The description only groups the criteria into categories and adds no semantics beyond what the structured fields provide.

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 states a specific verb and resource ('Search recursively for files/folders') and enumerates the match criteria (name pattern, extension, size, date, owner), so the agent knows exactly what the tool does. It does not distinguish itself from siblings such as list_files or drive_search, which keeps it from a 5.

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 word 'recursively' and the criteria list suggest this is the tool for filtered discovery, but nothing says when to prefer it over list_files or drive_search. No exclusions or alternative routing are given.

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