Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-cancelDeployment

Idempotent

Cancels an in-progress deployment for a specified application in Dokploy, helping stop unwanted or stuck releases using the provided application ID.

Instructions

POST /application.cancelDeployment

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-cancelDeployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations supply openWorldHint and idempotentHint, and the description adds nothing beyond them. It does not say what state the deployment ends in, whether queued or running builds are stopped, whether the application must be deployed first, or what is returned; only the bare HTTP verb hints at a mutation.

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 a single line with no wasted words, but that is under-specification rather than conciseness. Nothing is front-loaded except a route string an agent cannot act on.

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

Completeness2/5

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

This is a mutating, open-world operation with no output schema and an undocumented parameter, so the description should carry substantial weight. It delivers none of it, leaving the agent to guess at side effects, preconditions, and return shape.

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?

With a single required parameter at 0% schema description coverage, the description carries the full burden and provides no meaning for applicationId. It neither states the expected format (name, numeric id, uuid) nor says what happens if the deployment does not exist.

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 only the HTTP route 'POST /application.cancelDeployment', which restates the tool name rather than explaining what happens when a deployment is cancelled. It tells an agent nothing about effect, scope, or outcome, and gives no basis for distinguishing it from sibling tools like application-dropDeployment 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 Guidelines2/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 prerequisites, and no mention of alternatives. The crowded sibling set (compose-cancelDeployment, application-dropDeployment, deployment-killProcess, application-killBuild) makes a routing hint essential, and none is provided.

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