Skip to main content
Glama
adrojis

tracecat-mcp-community

by adrojis

tracecat_delete_workspace

Permanently delete a workspace and all its associated workflows, cases, and data. This action is irreversible.

Instructions

Delete a workspace (IRREVERSIBLE — deletes all workflows, cases, and data inside)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_idYesWorkspace ID (UUID)
Behavior4/5

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

With no annotations provided, the description carries full burden. It clearly states the mutation is irreversible and deletes associated content (workflows, cases, data). This adds behavioral context beyond a simple 'delete' operation, though it could further clarify permissions or side effects.

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?

Single sentence that is front-loaded with the action and includes a critical warning. No redundant information; every word adds value.

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 one-parameter tool with no output schema, the description adequately covers the purpose and consequences. It explains what gets deleted. However, it could mention any restrictions (e.g., cannot delete default workspace or permission requirements) for full completeness.

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?

Schema coverage is 100% with description for workspace_id as 'Workspace ID (UUID)'. The description does not add additional parameter semantics beyond the schema, so baseline of 3 is appropriate.

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?

Description clearly states 'Delete a workspace' with explicit verb and resource. The addition of 'IRREVERSIBLE — deletes all workflows, cases, and data inside' distinguishes it from other delete tools (e.g., tracecat_delete_workflow) by specifying the full scope of deletion.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The warning about irreversibility is present, but there is no mention of prerequisites, conditions, or when to prefer this over other deletion tools among the many siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adrojis/tracecat-mcp-community'

If you have feedback or need assistance with the MCP directory API, please join our Discord server