Skip to main content
Glama

Rename or move on webspace

webspace_rename
Destructive

Rename or move a file or directory inside a webspace as its site user, jailed to the home directory. An existing file at the target is not replaced; the call fails instead. Moving files out of public_html takes them off the website. For a VPS use vps_rename.

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": {
      "id": "<id>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "webspace_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
toYesNew path, same rules; must not exist yet
fromYesCurrent path. Path relative to the webspace's home directory, or absolute under /home/<user>/. The web root is public_html.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds genuinely new behavior: no overwrite of an existing target (the call fails), the site-user/home-directory jail, and the consequence that moving out of public_html takes files off the website. This explains why the operation is destructive, which the annotations alone do not. Return value is left unstated, but no output schema exists.

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?

Four compact sentences, front-loaded with the verb and scope, then the overwrite behavior and the VPS alternative. Each sentence carries information; no filler or redundancy beyond the mild repeat of the overwrite rule already implied by 'to must not exist'.

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 three-parameter mutation tool with full schema coverage and annotations declaring destructiveness, the description supplies the two things an agent most needs: target-overwrite behavior and the website-visible consequence of moves. Only the result of a successful call (e.g., new path returned) is unspecified.

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 each of the three parameters already carries its own description, including path rules for 'from' and the non-existence requirement for 'to'. The prose largely restates what the schema says, though the public_html note adds a little path context; 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?

Names a specific verb (rename or move) and resource (file or directory inside a webspace), plus the execution context ('as its site user, jailed to the home directory'). It explicitly distinguishes itself from the sibling vps_rename, so an agent can route without opening the schema.

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

Usage Guidelines4/5

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

Gives a clear routing rule to the alternative tool ('For a VPS use vps_rename'), which is the main ambiguity for a rename operation. It stops short of covering other decision points, such as when to delete-and-recreate instead of move, but the essential context is present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.