Skip to main content
Glama

Keelen

by io.github.jamie7893
OverviewDiscussionsAdmin

Delete Project

delete_project
Destructive

Soft-delete a project (the harder option) — frees a slot and hides it.

Stops any in-flight machine, then flips the project to `deleted`: it
disappears from `list_projects`, drops out of the project cap, and the loop
stops dispatching it. Deleting ALSO permanently purges the project's stored
review artifacts. The row is retained for audit and re-importing the repo
restores that deleted row in place (unlike `archive_project` there is no
in-tool restore), but the purged artifacts are gone for good and the stopped
workers' process state cannot be recreated. A replay on a deleted project
changes no row; the call is not idempotent end to end. Owner-scoped; a
project not in the workspace 404s.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

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 declare destructiveHint=true and idempotentHint=false, and the description adds substantial context beyond them: stops in-flight machines, frees a cap slot, purges review artifacts permanently while retaining the audit row, re-import restores the row in place, and a replay changes no row. It also discloses owner-scoping and 404 behavior.

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 core operation and its slot-freeing effect, then layers consequences. The density of parentheticals and backticked states makes it heavier than necessary, but nearly every clause carries distinct behavioral information.

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 single-parameter operation with an output schema already documenting returns, the description covers the full decision surface: reversibility, artifact loss, audit retention, idempotency, scoping, and error behavior. Nothing an agent needs to call it safely 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 description coverage is 0% on the single project_id parameter, so the description must compensate. It clarifies owner-scoping and that a non-workspace project 404s, which adds real meaning, but gives no ID format or example, so it only partially fills the gap.

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 and resource ('Soft-delete a project') and immediately scopes it against the sibling alternative ('the harder option', 'unlike archive_project'). An agent can distinguish it from archive_project and list_projects without opening any schema.

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 names archive_project as the softer alternative and contrasts the trade-off ('there is no in-tool restore' vs. re-import restoring the row). It conveys clear usage context but never states a crisp 'use this when X / avoid when Y' rule, so a 4 rather than a 5.

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

All Keelen toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources