Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-delete

Destructive

Delete a Dokploy application by its applicationId to remove it from your deployment setup.

Instructions

POST /application.delete

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

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds nothing beyond the HTTP method and path: it does not say whether deletion is permanent, what related resources are cascaded, whether confirmation or elevated auth is required, or how failures surface.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity reflects under-specification rather than economy. A raw route string is not a front-loaded statement of purpose and wastes the one sentence available.

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

Completeness1/5

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

For a destructive, open-world mutation with an undocumented required parameter and no output schema, the definition omits everything an agent needs: consequences of the call, identifier semantics, and return behavior. Nothing beyond the endpoint path is communicated.

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

Parameters2/5

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

There is a single required parameter, applicationId, with 0% schema description coverage, so the description carries the full burden of explaining it. It provides no information about the identifier's format, source, or whether it accepts a name or slug, leaving the agent to guess.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a bare route restatement, 'POST /application.delete', which merely echoes the tool name's verb and resource. It never states what an 'application' is in this system, what deletion entails, or how it differs from siblings such as application-cancelDeployment, application-clearDeployments, or application-dropDeployment.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no preconditions, and no mention of alternatives. An agent must infer from the name alone that this is the permanent-removal path rather than any of the several other application-scoped destructive-looking siblings.

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