Skip to main content
Glama

Delete a project

delete_project
DestructiveIdempotent

Removes a project from public serving into its recovery window. Requires the explicit deployments:delete scope and the exact project-name confirmation.

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>",
      "confirmation": "<confirmation>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "delete_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
confirmationYes
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description still adds real context beyond them: the deletion is reversible only within a recovery window, a specific OAuth-style scope is required, and an exact-name confirmation is enforced — all behavior an agent would otherwise have to guess.

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?

Two sentences, zero filler, with the most consequential fact (recoverable deletion) placed first and the preconditions second. Nothing repeats the name or the annotations verbatim.

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 three-parameter destructive tool with annotations covering the safety profile and no output schema, the description covers the essential unknowns: recoverability, required scope, and confirmation semantics. It stops short of saying what happens once the recovery window lapses or how a restore is performed, which would help an agent advise the user.

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 67%: project_id and idempotency_key are documented in the schema, but the confirmation parameter has no schema description. The description partially fills that gap by saying it must be the exact project name, though it does not restate the maxLength or specify whether it is the name or the prj_ ID that must be supplied verbatim.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Removes a project") and adds the crucial nuance that this is a soft removal into a recovery window rather than an immediate hard delete. It does not name a sibling it is not (e.g., rollback_project), so an agent must infer the boundary from the sibling list rather than the text.

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

Usage Guidelines3/5

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

Usage is implied by the verb and gated by stated prerequisites (deployments:delete scope plus exact project-name confirmation), which tells the agent what must be true before calling. However, there is no explicit when-to-use versus when-to-use-something-else guidance, such as preferring rollback_project for reverting a bad deploy instead of deleting the project.

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