Skip to main content
Glama

Delete application

delete_application
Destructive

Delete an Application: removes the platform resource and its pipeline wiring, and tears down every deployment of it on every cluster. To take it off one cluster only, use remove_application_deployment instead. Deletion is permanent.

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>"
    },
    "name": "delete_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes further by enumerating what actually gets destroyed — platform resource, pipeline wiring, and deployments across all clusters — plus stating deletion is permanent. That blast-radius detail is not derivable from the annotations.

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 short clauses, front-loaded with what is removed, followed by the sibling escape hatch and the permanence warning. No redundant restatement of the title and nothing padding the text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-param destructive tool with no output schema, the description covers blast radius, irreversibility, and the narrower alternative. The only omission is any mention of confirmation or authorization requirements, which annotation coverage partially implies.

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?

One parameter with 100% schema description coverage, so the schema already explains application_id. The description adds no format, sourcing, or lookup guidance beyond what the schema provides, which is the expected baseline for a fully documented single param.

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 (delete) and resource (Application), then defines scope precisely: removes the platform resource, its pipeline wiring, and every deployment on every cluster. This distinguishes it from remove_application_deployment without requiring the schema to be opened.

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

Usage Guidelines4/5

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

Explicitly names the alternative (remove_application_deployment) and the condition that selects it: taking the app off one cluster only. No exclusions against the broader destructive siblings like delete_stack or delete_resource, but the single most likely confusion is resolved.

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.