Skip to main content
Glama

Delete webspace

webspace_delete
Destructive

Delete a free webspace permanently. Requires confirm: true. Paid webspaces cannot be deleted; use webspace_cancel, which removes them when the paid period ends.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the description's value is the added context: deletion is permanent and requires an explicit confirm:true gate. It does not describe what happens to hosted files/data or any post-delete response, which keeps it below a 5.

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, front-loaded with the action and permanence, then the confirm requirement, then the alternative route. No redundant or filler wording.

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 two-parameter destructive tool with annotations and no output schema, this covers scope, safety gate, and the sibling routing. Minor gap: no note on whether deletion removes files/domains or is reversible in any window.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: 'id' is documented inline, but 'confirm' has no schema description beyond const:true. The description supplies the missing meaning by framing confirm as a required safety acknowledgment, adding value beyond the schema shape.

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?

States a specific verb (delete), resource (webspace), scope (free), and effect (permanently), and explicitly distinguishes itself from webspace_cancel in the same sentence set.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use (free webspaces), a when-not (paid webspaces cannot be deleted), and names the correct alternative (webspace_cancel) with the condition that selects it.

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.