Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-dropDeployment

Idempotent

Remove a deployment from a Dokploy application to clear unwanted deployment records and manage application deployment history.

Instructions

POST /application.dropDeployment

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "application-dropDeployment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations supply idempotentHint=true and openWorldHint=true but notably no destructiveHint, so the destructive character of a "drop" operation is left entirely undisclosed. The description says nothing about irreversibility, what artifacts are removed, required permissions, or side effects on running processes — it adds zero context beyond the route string.

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?

It is a single short line with nothing superfluous, and the only information present is front-loaded. The problem here is under-specification rather than verbosity.

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 deployment-removal operation with no input parameters, no output schema, and no destructiveHint annotation, the description would need to explain what is dropped and with what consequences. Instead it provides only an HTTP route, leaving an agent unable to judge safety or scope before invoking it.

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?

The tool takes no parameters and the schema coverage is 100%, so there is no parameter meaning for the description to explain. Baseline for a zero-parameter tool applies; the remaining concern that the tool implicitly targets some ambient application context is not a parameter-semantics issue.

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?

"POST /application.dropDeployment" only restates the operation ID as an HTTP route; the only signal about what it does is the word "drop" embedded in the path. It does not say what is dropped, and it gives no basis for distinguishing it from siblings such as deployment-removeDeployment, application-cancelDeployment, or application-clearDeployments.

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, when-not-to-use, prerequisite, or alternative-selection guidance of any kind. An agent has nothing to decide between this tool and the many deployment-removal 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