Skip to main content
Glama

Remove application deployment

remove_application_deployment
Destructive

Remove one deployment of an Application: take it off one cluster and namespace while the Application itself and its other deployments stay. Ankra uninstalls the workloads there - and with them any data in that deployment's database and volumes - and deletes the installation once the cluster has it. The Application, its settings, secrets, images and release history, its other installations, and add-ons other workloads may use are kept, so it can be deployed there again. Accepted is not done: the installation reads 'removing' until the teardown finishes (list_application_installations), or 'failed' with its reason. Refused with a conflict when that deployment is already being removed, and when nothing is deployed there. Use list_application_installations first to find the cluster and namespace. A deployment the deploy wizard made has no installation: name it by stack_name instead of namespace (get_application_deployments lists it as a deploy_run_stack row); the other stacks that deploy created stay and are named in the answer. To stop it for a while without losing anything, use park_application_deployment instead; to delete the Application everywhere, delete_application.

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_id": "<application_id>",
      "cluster_id": "<cluster_id>"
    },
    "name": "remove_application_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceNoNamespace the deployment runs in (part of the deployment's identity - one application can be deployed twice on one cluster). Pass this or stack_name, not both.
cluster_idYesUUID of the cluster the deployment runs on.
stack_nameNoStack a deploy-wizard deployment runs as, for a deployment with no installation (get_application_deployments lists it as a deploy_run_stack row). Pass this or namespace, not both.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond destructiveHint=true by saying exactly what is destroyed (workloads plus data in that deployment's database and volumes) versus what survives (Application, settings, secrets, images, release history, other installations, shared add-ons). It also discloses the async lifecycle ('removing' until teardown finishes, or 'failed' with a reason), the conflict conditions, and the no-installation deploy-wizard path where sibling stacks persist.

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-loads the core action and scope, then layers consequences, async state, error conditions, prerequisites, and alternatives in a logical order. It is long, and the list_application_installations reference recurs (lookup and status checks), but nearly every sentence carries information an agent needs before a destructive call.

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, asynchronous, variant-heavy tool with no output schema, the description covers the outcome semantics (installation status, conflict responses, what the answer names back). An agent has enough to select the tool, pick the right identifier, and interpret the result without guessing.

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: namespace vs stack_name are an identity choice for the same deployment, and stack_name applies specifically to deploy-wizard deployments that have no installation and appear as deploy_run_stack rows in get_application_deployments. The mutual-exclusion rule is largely duplicated from the schema, which keeps it below a 5.

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 precise verb and scoped resource: remove ONE deployment of an Application from one cluster and namespace, while the Application and its other deployments stay. It immediately distinguishes the operation from siblings by naming delete_application (delete everywhere) and park_application_deployment (stop temporarily).

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?

Explicitly routes the agent: call list_application_installations first to find cluster and namespace, use park_application_deployment to pause without data loss, use delete_application to remove the Application everywhere. It also gives the negative precondition (refused when nothing is deployed there) and the deploy-wizard case that requires stack_name instead of namespace.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.