Skip to main content
Glama

rename_or_move

Rename, move, or copy files and directories on a cPanel server by specifying a source path, an operation, and a destination, so you can reorganize hosted content without SSH.

Instructions

Rename, move, or copy a file or directory on the cPanel server.

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": {
      "operation": "<operation>",
      "source": "<source>",
      "destination": "<destination>"
    },
    "name": "rename_or_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesRelative path of the source file or directory.
operationYesOperation type: rename, move, or copy.
destinationYesFor 'rename': the new file/folder name only. For 'move'/'copy': target directory relative path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether operations overwrite existing files, how permissions are handled, whether directories are copied recursively, or what errors may occur, which is a significant gap for a filesystem mutation tool.

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?

The description is a single, front-loaded sentence with no wasted wording. It immediately communicates the core purpose and scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is too sparse. While parameter semantics are fully covered by the schema, critical behavior such as overwrite handling, permission requirements, and operation-specific effects is omitted.

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 100%, so the input schema already documents all three parameters, including the operation enum and destination semantics. The description itself adds little beyond restating the operation types, so the baseline of 3 applies.

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 specific verbs and resource: rename, move, or copy a file or directory on the cPanel server. It is clear what the tool does, though it does not explicitly differentiate itself from siblings like write_file or create_folder.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description only defines the capabilities, leaving the agent to infer appropriate usage contexts.

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