Skip to main content
Glama

Rename or move on VPS

vps_rename
Destructive

Rename or move a file/directory on a VPS via SSH.

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": "vps_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
toYesAbsolute destination path
fromYesAbsolute source path

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered structurally. The description adds the useful detail that the operation runs over SSH on the remote filesystem, but it omits behavior an agent would want for a destructive move: whether an existing destination is overwritten, whether parent directories are created, and what happens on partial failure.

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?

A single well-formed sentence with the operation and the resource front-loaded and no filler. It is arguably under-specified rather than padded, so the brevity is a virtue but does not earn top marks on its own.

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

Completeness3/5

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

For a three-required-parameter destructive filesystem operation with full schema coverage and no output schema, the definition is minimally viable. It leaves the destructive edge cases (overwrite of an existing destination, permission errors, atomicity of the move) unexplained, which is the main gap for this class of tool.

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%, with each of the three parameters (id, from, to) documented as VPS ID and absolute source/destination paths, so the baseline is 3. The description contributes nothing further about path formatting, whether 'from' must exist, or whether 'to' may equal 'from'.

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 pairs specific verbs (rename/move) with a specific resource (file/directory) and even names the transport (SSH), so an agent knows exactly what the operation does. It does not, however, differentiate itself from the sibling webspace_rename, leaving the agent to infer that this one applies to VPS instances rather than webspaces.

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 explicit when-to-use or when-not-to-use guidance and no mention of prerequisites such as existing SSH access or the destination path being reachable. The only usage signal is the implicit 'move a file' semantics of the verb, which the agent must infer.

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.