Skip to main content
Glama

Delete one application version

edgegap_delete_app_version
DestructiveIdempotent

Delete a specific application version to clean up test builds; running deployments block deletion, and without confirm: true the result only previews the change.

Instructions

Delete one version of an application, to clean up test versions. Exactly one exact version name; refused while any deployment of that version is running. The container image stays in the registry (edgegap_delete_registry_tag removes it). 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>",
      "version": "<version>"
    },
    "name": "edgegap_delete_app_version"
  }
}

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.
versionYesThe exact version name to delete.
applicationYesApplication name.

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.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint and idempotentHint, but the description adds substantive context: the operation is refused while deployments are live, the registry image is left behind, and the action is irreversible. It also discloses the confirm-gating behavior, so the agent knows a call without confirm: true is a no-op preview rather than a deletion.

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?

Three dense sentences with no filler; the destructive consequence and the deployment precondition are front-loaded ahead of the sibling cross-reference and the confirm caveat.

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 tool with no output schema, the description covers what is destroyed, what survives (the registry image), the precondition that blocks deletion, and the confirmation flow. Nothing an agent needs in order 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 100%, so the confirm, dry_run, version, and application parameters are already fully documented in structured fields. The description reinforces the cardinality ("exactly one exact version name") and the confirm preview semantics, but this largely restates the schema rather than adding new parameter meaning.

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 ("Delete one version of an application") plus a scope qualifier (test-version cleanup). It explicitly separates itself from edgegap_delete_registry_tag by noting the container image stays in the registry, so an agent can distinguish it from the obvious delete siblings.

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 both the positive case (cleaning up test versions) and the blocking condition (refused while any deployment of that version is running). It also routes the agent to edgegap_delete_registry_tag for the related but distinct image-removal task.

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