Skip to main content
Glama

Delete a workspace

delete_workspace
Destructive

Permanently deletes a workspace and all its content; preview first, then pass confirm=true to execute.

Instructions

Permanently deletes a workspace and its content. Requires confirm=true — first call WITHOUT confirm to preview, show the user, then call again with 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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "delete_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to delete. Omit/false returns a preview only.
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.1/5.0
Behavior4/5

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

destructiveHint=true already flags danger, but the description adds what annotations cannot: that deletion is permanent and cascades to workspace content, and that a preview mode exists as a safe dry run. It does not cover required permissions or whether the operation is recoverable.

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?

Two sentences, zero waste: the destructive effect is front-loaded and the two-step confirm sequence follows immediately. Nothing redundant and nothing padded.

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 two-parameter destructive tool with no output schema, the definition covers effect scope and the confirmation protocol, which is what an agent needs to call it safely. Minor gaps remain around permissions and the shape of the preview response.

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 only 50% (confirm is documented, workspaceId is not). The description compensates by explaining the confirm workflow as a two-call sequence and implicitly tying workspaceId to the target workspace, adding meaning beyond the bare boolean description in the schema.

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?

"Permanently deletes a workspace and its content" gives a specific verb, resource, and scope (the content goes with it), which hints at the boundary versus delete_workspace_data. It stops short of explicitly naming that sibling, so the agent must infer the distinction.

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?

The description gives an explicit call protocol: first invoke without confirm to get a preview, show it to the user, then re-invoke with confirm:true. That is clear procedural guidance for the destructive path, though it never states when to prefer a narrower sibling like delete_workspace_data.

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