workspace_delete
Permanently delete this workspace and all governed contents after active-work checks. The client must obtain confirmation and pass confirm=true. The MCP endpoint stops existing after success.
When to use it
Use workspace_delete to delete the authenticated workspace. This tool operates at workspace scope. It does not require a project context unless a filtering argument explicitly asks for one.
Only a workspace owner can discover this tool. Deleting a workspace is permanent; obtain explicit confirmation before calling it.
Arguments
| Name | Type | Required | Default | Constraints |
|---|---|---|---|---|
confirm | boolean | Yes | — | Must equal true |
View the complete input schema, including nested contracts and alternative shapes. The schema is extracted from the workspace server’s Zod definitions. Runtime validation also enforces custom checks that JSON Schema cannot express.
Response shape
The operation-specific payload is returned in data; its contents follow the operation described above.
MCP returns a text block containing the JSON operation result and a
structuredContent copy. The envelope includes data, completeness,
truncated, freshness, and warnings. Depending on the operation it can also
include nextCursor, evidence, job, or receipt.
Check those fields before treating a conversational summary as the result.
When a job is returned, inspect its status with the appropriate execution tool;
a queued response is not confirmation that work finished. Follow evidence links
when checking the underlying records.
Input methods
This request illustrates the argument structure. Replace every angle-bracket placeholder with a real value and supply any applicable optional fields from the schema. Nested business contracts must match your actual configuration. Send it through an authenticated, initialized MCP client; this JSON alone does not establish a session or sign you in.
Use Semogram’s workspace_delete tool to delete the authenticated workspace. Inspect the required inputs and target first, then show me what will change before executing it.
Use real resource IDs returned by earlier reads; a resource name is not a UUID. Do not fill missing business inputs with invented values.
This is an MCP tools/call request, not a form to paste into Semogram. Send it through an authenticated, initialized MCP client.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "workspace_delete",
"arguments": {
"confirm": true
}
}
}FAQ
What access and approvals are required?
Required permission scopes: org:manage.
OAuth uses current workspace membership; API keys use their assigned scopes
and grants. Discovery can exclude tools the caller cannot use.
Read-only annotation: No. Destructive annotation: Yes.
The schema requires confirm: true. Ask the user to review the exact target and approve the operation before calling it.
How should I handle retries?
Do not assume repeated calls are safe merely because the client offers Retry. Inspect the result or existing request before repeating work that changes state. For 429 responses, honor Retry-After rather than retrying immediately.
Why is this tool missing or returning an error?
Only a workspace owner can discover this tool. Deleting a workspace is permanent; obtain explicit confirmation before calling it. See connection, authentication and troubleshooting for sign-in, scope, resource access, and rate-limit errors.