rename_item
Rename a file or folder on a zspace NAS by specifying its full path and new name.
Instructions
重命名 zspace NAS 上的文件或文件夹
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | 文件/文件夹的完整路径,如 /sata12/my/data/旧名称 | |
| newname | Yes | 新名称(仅名称,不包含路径) |
Rename a file or folder on a zspace NAS by specifying its full path and new name.
重命名 zspace NAS 上的文件或文件夹
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | 文件/文件夹的完整路径,如 /sata12/my/data/旧名称 | |
| newname | Yes | 新名称(仅名称,不包含路径) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description bears full burden. It mentions renaming but lacks details on side effects (e.g., overwrite behavior), permissions, or error conditions. Minimal behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no extraneous text. Efficiently states purpose. Could be slightly expanded for clarity without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple rename operation with two well-documented parameters, the description is adequate. However, it lacks information on return values, error handling, and differentiation from move_item.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with clear parameter descriptions. The tool description adds no extra meaning beyond what is already in the schema, so baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb '重命名' (rename) and the resource 'zspace NAS 上的文件或文件夹' (files/folders on zspace NAS). It distinguishes from siblings like copy_item, move_item, and delete_item.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives (e.g., move_item can also rename). No exclusions or context for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/philipxiaoxi/z-cli'
If you have feedback or need assistance with the MCP directory API, please join our Discord server