Skip to main content
Glama

Delete project

delete_project
DestructiveIdempotent

Delete a project permanently

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

Input Schema

NameRequiredDescriptionDefault
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is largely covered. The description's only addition is the word "permanently," which usefully reinforces irreversibility but says nothing about cascading effects on the project's files, databases, domains, or share links, nor about confirmation requirements.

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?

Four words, front-loaded with the verb and carrying no filler. It is efficient, though the brevity edges toward under-specification rather than disciplined conciseness for a destructive operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an irreversible, open-world destructive operation, and the definition says nothing about what else is destroyed, whether recovery is possible, or what the response confirms. Annotations carry the destructive flag, but the description leaves the blast radius of a project deletion entirely unexplained.

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 description coverage is 0%, but there is only one required parameter, project_id (string), whose meaning is fully self-evident from its name. The description adds no detail on ID format or where to obtain the ID, so it neither compensates for the coverage gap nor causes real ambiguity.

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?

"Delete a project permanently" names a specific verb (delete) and resource (project), so the action is unambiguous. It does not distinguish itself from siblings such as delete_file, delete_share_link, or storage_delete_object, but the resource noun is distinctive enough that confusion is unlikely.

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?

There is no guidance on when to choose this over alternatives like update_project, export_project, or delete_file, nor any precondition such as ownership or required permissions. The agent must infer entirely from the name that this is the sole project-removal path.

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