Skip to main content
Glama
Sign In
mcp-synology

mcp-synology

by cmeans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

rename

Rename a file or folder in place on your Synology NAS by supplying its path and a new name; DSM rejects the change if the name is already taken, so nothing is overwritten.

Instructions

Rename a file or folder in place. If the new name is already taken in that folder, DSM refuses and nothing is replaced. To move something to another folder, use move_files.

Input Schema

NameRequiredDescriptionDefault
pathYesThe file or folder to rename (`/video/TV Shows/Severence`).
new_nameYesThe new name only, not a path (`Severance`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.1
    • addedInput schema / properties / new_name / description
      Added value: +"The new name only, not a path (`Severance`)."
    • addedInput schema / properties / path / description
      Added value: +"The file or folder to rename (`/video/TV Shows/Severence`)."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "tool_renameOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.7.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-destructive, non-read-only mutation, and the description adds the important failure semantics: a name collision is refused and nothing is replaced. It stops short of saying what the response looks like or whether the operation is atomic, but the key risk behavior is disclosed.

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 short sentences, each doing work: what it does, what happens on conflict, and where to go instead. Front-loaded and free of 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?

For a two-parameter mutation with full schema coverage, this covers purpose, conflict behavior, and the sibling alternative. Minor gaps remain (return value, whether folders recurse or any permission prerequisites), but nothing needed to call it correctly 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% and both parameters have examples showing full path vs. bare name. The description's 'new name ... in that folder' reinforces the scoping but adds little beyond the schema itself, 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 ('Rename a file or folder') and adds the scope qualifier 'in place', which cleanly separates it from move_files. An agent can pick between the two without opening either schema.

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 names the alternative ('use move_files') and the condition that selects it (moving to another folder). It also states the use case this tool does cover, so both branches of the decision are given.

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