Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Delete Workspace

delete_workspace
DestructiveIdempotent

Permanently removes an empty Meshive workspace after a preview and confirmation, refusing deletion while blockers remain and requiring admin or billing role.

Instructions

Delete an empty workspace (it needs the admin or billing role). This can't be undone. workspace is required and never picked for you: pass its id, or its label for the preview. A workspace that still holds anything is refused (workspace_not_empty) and blockers counts what is left: pods, storage, servings, tasks (finished ones too), task outputs still being saved, assets, custom templates and models, credentials, webhooks, inference keys, other members, open invitations, pending payouts and operations in progress. Follow its next_step, and clear nothing the user didn't ask you to. With confirm=false (default) it only checks and deletes nothing; call again with the workspace id and confirm=true after the user agreed (a label is refused there). Deletion runs in the background: the workspace leaves the list within a moment. Its name becomes available when deletion finishes. Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.

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": {
      "workspace": "<workspace>"
    },
    "name": "delete_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
workspaceYes
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond destructiveHint=true, the description discloses what is irreversible ('can't be undone'), the refusal code workspace_not_empty and the full semantics of the blockers counter, background deletion timing ('leaves the list within a moment', name freed only when deletion finishes), and operation_id retry semantics. This is materially more than the annotations provide.

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?

Front-loaded with the verb and the irreversibility warning, then organized into check → confirm → background-completion. It is dense and parenthetical (the long blockers enumeration), but nearly every clause carries operational information an agent needs for a destructive multi-step call.

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

Completeness5/5

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

With an output schema available, the description rightly omits return-value detail and instead covers the risks unique to this tool: role requirement, emptiness precondition, refusal handling, delayed completion, and operation_id lifecycle. Nothing needed to call it safely is missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description must carry the load and it does: workspace accepts an id or a label (label only for preview), confirm defaults to false and deletes nothing, and operation_id must be reused from the preview or generated as a UUID before the first call and kept across retries.

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 and resource ('Delete an empty workspace') plus the role precondition ('admin or billing role'). The 'empty' qualifier and the explicit note that a non-empty workspace is refused clearly separate it from update_workspace/create_workspace.

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 two-phase protocol: call with confirm=false (default) to only check, then call again with the workspace id and confirm=true after the user agrees, with the added rule that a label is refused at that stage. It also names the follow-up paths (next_step, operation_status) and warns not to clear anything the user didn't ask to clear.

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