Skip to main content
Glama

project_delete_confirm

DestructiveIdempotent

Confirm project deletion using the 6-digit code returned by project_delete. Human authorization is required. Confirmation immediately takes the project and its hostnames offline, blocks new project effects, retains its database, files, functions, environment variables, and domain bindings for 30 days, and schedules permanent erasure after that retention period. Recovery during the retention period requires support.

Example:

{ "project_id": "my-saas", "code": "482917" }

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_id": "<project_id>",
      "code": "<code>"
    },
    "name": "project_delete_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes6-digit code returned by project_delete. Expires 10 minutes after it was issued.
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive/non-readonly, and the description goes well beyond them: it details immediate offline status, blocked effects, 30-day retention of data/files/env vars, scheduled permanent erasure, and that recovery requires support. That is exactly the context an agent needs before an irreversible action.

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 action and the human-authorization gate, then consequences. The retention detail is dense but necessary; the JSON example is a modest addition that pays for itself.

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, irreversible confirmation tool with no output schema, the definition covers prerequisites, timing, what happens immediately, what is retained, and how recovery works. Nothing material 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 the schema already defines both fields and their formats; the description's example adds a concrete shape but no new semantic constraints. Baseline 3 applies.

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 (confirm) and resource (project deletion) plus the mechanism (6-digit code from project_delete), which cleanly distinguishes it from the sibling project_delete that issues the code.

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?

Explicitly frames this as the second step of a two-step flow, requires human authorization, and the schema adds the 10-minute code expiry. No explicit 'do not use if...' exclusions, but the prerequisite chain is clear enough for correct invocation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources