SynoLink defines 7 tools with basic schemas and descriptions. All tools have input schemas with type definitions and descriptions present. However, descriptions are minimal (10-50 chars), falling below the 50-200 char baseline for LLM-optimized descriptions. No output schemas are documented. Error handling is absent, tools return raw API responses without recovery guidance. Parameter descriptions lack format constraints, ranges, or examples. No tool annotations (readOnlyHint/destructiveHint) despite clear risk distinctions (5 READ_ONLY, 2 WRITE). Naming is verb-first and clear (list_, read_, write_, create_, search_, get_), following conventions. No composition issues detected, tools are single-responsibility. Security: credentials passed as CLI args (not ideal but not exposed in tool params). Overall: functional but minimal quality, typical of community servers.
Create a new directory on the Synology NAS
Get detailed information about a file on the Synology NAS
List contents of a directory on the Synology NAS
List all shares available on the Synology NAS
Read the contents of a file from the Synology NAS
Search for files matching a pattern in a directory on the Synology NAS
Descriptions are too brief (10-50 chars vs. 50-200 char baseline). LLMs cannot determine when to select tools or understand prerequisites. E.g., 'List all shares available on the Synology NAS' lacks context on when to call it vs. list_directory.
No output schemas documented. LLMs cannot plan downstream calls or extract required fields. E.g., does list_shares return share names, paths, permissions? Does read_file return raw content or {content, encoding, size}?
No error handling or recovery guidance. Tools return raw API errors without actionable next steps. E.g., 'Login failed' or 'Path not found', no suggestion to check credentials or try a different path.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | <=2025-11-25 | v2 |
Write content to a file on the Synology NAS
No tool annotations despite clear risk distinctions. write_file and create_directory are destructive (WRITE risk), but lack destructiveHint annotation. read_file, list_*, search_*, get_file_info are READ_ONLY but lack readOnlyHint. Agents cannot reason about safety.
Parameter descriptions lack format constraints. 'path' param says 'must be absolute path with leading slash' but no regex pattern or example. 'pattern' in search_files has no description of glob/regex syntax. LLMs guess at valid formats.