Skip to main content
Glama

Delete file or directory on VPS

vps_delete_path
Destructive

Delete a file or directory on a VPS via SSH. Refuses critical system paths (/, /usr, /etc, /var, /home). Destructive: requires confirm=true.

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>",
      "path": "<path>",
      "confirm": "<confirm>"
    },
    "name": "vps_delete_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
pathYesAbsolute path to delete
confirmYesMust be true to confirm this destructive operation
recursiveNoDelete directories recursively (default false)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/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, so the description is not carrying the basic safety burden. It nevertheless adds genuinely new behavior: the operation runs over SSH, a hardcoded blocklist of critical paths is refused server-side, and confirm=true is mandatory — all facts absent from the structured fields. It stops short of saying whether deletion is recoverable or what happens to a non-empty directory without recursive.

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?

Three short sentences, front-loaded with the action and followed by the guardrail and the confirmation requirement. Every sentence carries information; no filler or redundant restatement of the title.

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 simple four-parameter mutation with no output schema and full annotation coverage, the description covers purpose, mechanism, refusal behavior, and the confirm precondition. The main residual gap is the semantics of recursive on non-empty directories and the post-delete result, neither of which is stated.

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 all four parameters (id, path, confirm, recursive) are already documented in the schema. The description reinforces the confirm semantics and the file-vs-directory target but adds no new detail, and never mentions recursive, so baseline 3 is appropriate.

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?

States a specific verb (delete) and resource (file or directory) plus the mechanism (via SSH) and scope (on a VPS). It does not explicitly distinguish itself from the sibling webspace_delete_path, so an agent must infer the VPS-vs-webspace split from the name alone.

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

Usage Guidelines3/5

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

Usage context is implied by the scoping guardrails (refuses critical system paths, needs confirm=true), and the confirm requirement effectively signals when the call is legitimate. However, it never names an alternative or states when to prefer a different delete tool, leaving sibling routing to the name.

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.