Skip to main content
Glama

ui_delete_project

Permanently deletes a project by project_id, removing it from the work-plan server when it is no longer needed.

Instructions

App-only: permanently delete a project.

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": "ui_delete_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discharges only part of it: "permanently" correctly signals irreversibility, the single most important fact for a delete tool. It says nothing about whether child tasks/memories are cascaded or orphaned, what permissions or confirmation are required, or what happens if the project_id does not exist.

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?

A single short sentence with the destructive nature front-loaded by "permanently." Nothing is wasted, though the terseness leaves real gaps rather than achieving efficient density.

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

Completeness3/5

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

For a simple one-parameter tool with no output schema, the definition covers the essential purpose and irreversibility. It falls short on destructive-tool essentials — cascade behavior, permission requirements, and the meaning of "App-only" — which are exactly what a delete tool's description should supply when annotations are absent.

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?

One parameter at 0% schema coverage, and the description adds no semantics: it does not say whether project_id is a UUID, slug, or numeric handle, nor where to obtain it. The schema types it only as a string, so nothing compensates for the coverage gap.

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?

A specific verb plus resource: "permanently delete a project." The word "permanently" also implicitly distinguishes it from the sibling ui_archive_project, though the sibling is never named. The added "App-only" qualifier is unexplained but does narrow the scope.

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 explicit guidance on when to choose this over ui_archive_project or ui_update_project, and no statement of prerequisites, confirmation steps, or conditions in which deletion is inappropriate. "App-only" functions as a usage constraint, but it is undefined jargon (app UI only? not agent-callable? unavailable in some contexts?), so it does little to route the agent.

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