Skip to main content
Glama

Move project to trash

project_delete
Destructive

Permanently delete a project after user confirmation: sandboxes, volumes, and snapshots are removed immediately, while services and databases remain in trash for 3 days.

Instructions

Delete a project when its owner explicitly asks. Its services and databases stop and stay in trash for 3 days; its sandboxes, their volumes and snapshots are deleted at once and cannot be recovered. Tell the user both parts before asking. Requires the user's confirmation; do not call this to delete only one service.

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": {
      "project": "<project>",
      "confirm": "<confirm>"
    },
    "name": "project_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesSet only after the user approves deleting this project
projectYesProject name, slug, or ID; use an ID if names are ambiguous

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.7/5.0
Behavior5/5

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

Even though annotations already flag destructiveHint=true, the description discloses the actual blast radius: services and databases stop and linger in trash for 3 days, while sandboxes, their volumes, and snapshots are destroyed immediately with no recovery. It also prescribes telling the user both parts before asking, which annotations can't express.

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?

Four short sentences, front-loaded with the action and its precondition, then the consequences, then the confirmation rule. Nothing repeats the name or title and no sentence is filler.

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?

For a destructive, non-idempotent, closed-world two-parameter tool with no output schema, the description covers selection, preconditions, irreversible consequences, and user-confirmation obligations. Nothing an agent needs in order 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.

Parameters3/5

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

Schema coverage is 100%, so both the project identifier and the confirm const are already documented in the schema. The description reinforces the confirmation gating but adds no new syntax or formatting detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 a project) and immediately scopes it against the tempting wrong target: 'do not call this to delete only one service,' which distinguishes it from service_delete. An agent can pick this over service_delete or workspace_delete from the description alone.

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 precondition ('when its owner explicitly asks'), an explicit exclusion ('do not call this to delete only one service'), and a gating requirement ('Requires the user's confirmation'). Both when-to-call and when-not-to-call are stated outright.

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