Skip to main content
Glama

deployment_delete

Delete a deployment by ID, optionally cascading removal to running instances and history. Configure flags to skip custom listeners and I/O mappings when lifecycle hooks must be bypassed.

Instructions

Delete a deployment by ID. Set cascade=true to also delete running instances and history. Use skipCustomListeners and skipIoMappings to bypass lifecycle hooks.

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": {
      "id": "<id>"
    },
    "name": "deployment_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
cascadeNo
skipIoMappingsNo
skipCustomListenersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.3.0
    • addedInput schema / properties / cascade
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / skipCustomListeners
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / skipIoMappings
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the key destructive consequence: cascade removes running instances and history, and the skip flags bypass lifecycle hooks. That is meaningful context beyond a bare 'delete'. Missing are explicit irreversibility warnings, permission or auth requirements, and the default behavior of the skip flags when omitted.

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?

Three short sentences, front-loaded with the core action and then the optional flags. Every sentence carries information; nothing is redundant. Slightly terse given the destructiveness of the operation.

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 destructive tool with no annotations and no output schema, the definition covers parameters and deletion scope but omits whether the operation is irreversible, what happens on partial failure, or what error surfaces when instances exist without cascade. Adequate to invoke, not fully complete for safe operation.

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 description coverage is 0%, so the description must compensate, and it does explain the meaning of all three non-trivial parameters: cascade expands deletion scope, while skipCustomListeners and skipIoMappings bypass lifecycle hooks. Only gap is that defaults and the exact semantics of 'history' are not spelled out.

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 first sentence gives a specific verb plus resource ('Delete a deployment by ID'), which is immediately actionable and clearly distinct from read siblings like deployment_getById or deployment_list. It does not explicitly name siblings, but the verb 'Delete' does the differentiation work on its own.

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?

It gives conditional guidance for one flag ('Set cascade=true to also delete running instances and history'), which tells the agent when to escalate to a cascading delete. However, there is no when-not-to-use advice, no statement of what happens if a deployment has running instances and cascade is left false, and no mention of alternatives such as redeploying.

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