Skip to main content
Glama

Delete file or directory on webspace

webspace_delete_path
Destructive

Delete a file or directory inside a webspace (jailed). Refuses the home root. 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": "webspace_delete_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
pathYes
confirmYesMust be true to confirm this destructive operation
recursiveNo

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 safety profile is pre-supplied and the description correctly does not contradict it. It adds genuine context beyond the annotations: the operation is jailed to the webspace and refuses to target the home root. It stops short of saying whether deletion is irreversible or what happens to a non-empty directory, so it is not fully transparent.

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?

Three short sentences with the scope stated first, the hard exclusion second, and the safety requirement last. No filler or redundant restatement of the annotations.

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 destructive 4-parameter tool with no output schema, the description covers scope and the confirmation gate adequately. The remaining gap is the recursive parameter's behavior and the irreversibility of the delete, which are the details most likely to cause a wrong invocation.

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?

With schema coverage at 50%, id and confirm are documented in the schema, while path and recursive are not. The description partially compensates by establishing that path is jail-scoped and cannot be the home root. However, the important recursive flag is left unexplained, so an agent cannot tell from the definition whether a non-empty directory requires it.

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?

"Delete a file or directory inside a webspace (jailed)" is a specific verb plus resource, and the parenthetical scope plus "Refuses the home root" separates it from a whole-webspace delete. It never names an alternative sibling explicitly, but the path-level versus webspace-level distinction is clear from the wording 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?

The description gives one concrete constraint (paths at the home root are refused) and one prerequisite (confirm=true), which implicitly tells the agent when the call will be rejected. There is no explicit statement of when to prefer this over vps_delete_path or webspace_delete, so usage context remains inferred.

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.