Skip to main content
Glama

Delete an application and all its versions

edgegap_delete_app
DestructiveIdempotent

Permanently delete an application and all its versions to clean up test apps. Requires confirm to act, is blocked while deployments run, and previews the result otherwise.

Instructions

Delete one application and every version under it, to clean up a test application. Exactly one exact name; refused while any of its deployments is running, and refused when it has more versions than max_versions (default 0: delete its versions first with edgegap_delete_app_version, or raise max_versions after the developer agreed). Registry images are not touched. Cannot be undone, so without confirm: true the result only previews it and nothing is sent.

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": {
      "application": "<application>"
    },
    "name": "edgegap_delete_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet true only after the developer approved this exact call. Without it nothing is sent: the result previews what would be stopped or deleted (status "confirmation_required").
dry_runNoShow the exact request (method, host, path, body) with secrets masked, and send nothing. Local checks still run. Use it to confirm a billable or destructive call before making it.
applicationYesThe exact application name to delete.
max_versionsNoDelete only if it has at most this many versions. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.19.0
    • addedInput schema / properties / confirm
      Added value: +{
      +  "description": "Set true only after the developer approved this exact call. Without it nothing is sent: the result previews what would be stopped or deleted (status \"confirmation_required\").",
      +  "type": "boolean"
      +}
  2. Addedv0.15.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint and idempotency, and the description adds behavior they don't cover: refusal while deployments are running, the max_versions gate with its default of 0, that registry images are left untouched, that the delete is irreversible, and that without confirm: true nothing is sent and the result is only a preview.

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?

The action and its scope come first, followed by the preconditions and the preview rule. It is dense with chained clauses and slightly long as one sentence, but every clause carries distinct information and none is filler.

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, multi-param tool with no output schema, it covers everything an agent needs before calling: preconditions, the preview path, alternatives for the version-count block, and what is not affected (registry images). No output schema exists, so nothing needs to be said about return values.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about how parameters interact: the default max_versions of 0 effectively blocks deletion of any app with versions, and confirm gates the request entirely. It adds little on dry_run, but the interplay it explains goes beyond the per-field schema text.

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 with scope: 'Delete one application and every version under it.' It also names the sibling edgegap_delete_app_version as the per-version alternative, so an agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the intended situation ('clean up a test application') plus explicit refusal conditions (running deployments, version count above max_versions) and the two remedies: delete versions first with edgegap_delete_app_version, or raise max_versions after developer agreement. When-to-use and when-it-will-fail are both covered.

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