Skip to main content
Glama

Coline

Delete a project

delete_project
DestructiveIdempotent

Moves a project to the trash, where it can be restored. Its tasks stay on their boards.

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

Input Schema

NameRequiredDescriptionDefault
projectIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful context beyond them: the effect is reversible via the trash, and a key side effect (tasks remain on their boards rather than being deleted with the project) is disclosed.

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 short sentences, both front-loaded with the consequential fact first (it goes to the trash, it is restorable) and the secondary effect second. No filler words and nothing that could be trimmed without losing information.

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?

An output schema exists, so return values need not be explained, and the annotations cover safety and idempotency. The remaining gap is minor: no statement of required permissions or what happens if the project is already trashed, but for a two-parameter soft-delete tool the description is close to sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema description coverage is 50%, so the schema carries only partial meaning, and the description adds nothing about either parameter. It never mentions projectId (whose only documentation is length constraints) or that workspace is a slug obtainable from workspaces.list.

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 ("Moves a project to the trash") and immediately clarifies the operation is a soft delete rather than a permanent one. That distinguishes it materially from a hard-delete operation, though it does not name or contrast any sibling tool such as update_project.

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?

Guidance is implied rather than stated: saying the project "can be restored" from the trash tells an agent recovery exists, but there is no explicit when-to-use versus when-not, no mention of prerequisites or permissions, and no pointer to an alternative action for permanent removal.

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