Skip to main content
Glama

ai_modeling_project_delete

Destructive

Delete explicitly selected projects you own using their IDs. Remove outdated or unwanted Studio projects in a single batch operation.

Instructions

Delete explicitly selected projects you own.

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_ids": "<project_ids>"
    },
    "name": "ai_modeling_project_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this permanently removes data; the description's real contribution is the ownership restriction and the requirement that projects be explicitly enumerated. What is missing is whether deletion is recoverable (a restore sibling exists), what happens when one ID in a batch is unauthorized, and what the response contains. Solid but incomplete beyond the annotation baseline.

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 scope qualifiers front-loaded and no filler. It is efficient, though it is terse enough that the ownership consequence (failure vs skip) is left unstated.

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 one-parameter destructive tool with no output schema, the annotations cover the safety profile and the description covers scope and ownership. The gaps that matter for correct invocation are behavioral: irreversibility versus the restore path, and error semantics for non-owned IDs.

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%, so the description must carry the load. It does add meaning beyond the schema by implying project_ids must be concrete IDs of owned projects rather than a filter or wildcard, but it says nothing about the batch limits (1-100) or the ID character constraints, so half the burden remains unmet.

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 names a specific verb (Delete) and resource (projects), and adds two meaningful qualifiers: the projects must be explicitly identified and must be owned by the caller. It is unambiguous about what the tool does, though it does not explicitly contrast itself with the available restore sibling or the other delete tools.

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?

"Explicitly selected projects you own" implies the preconditions: the agent must already know the project IDs and must hold ownership. However, there is no guidance on when not to use it, no mention of the recovery path via ai_modeling_project_restore, and no guidance on partial failure handling when a mixed-ownership list is submitted.

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

Deploy Server

Other Tools