Skip to main content
Glama
MCP Dokploy Online
by igoruam

deployment-killProcess

Idempotent

Terminate a running deployment process by its deployment ID to stop stuck or unwanted Dokploy builds.

Instructions

POST /deployment.killProcess

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": {
      "deploymentId": "<deploymentId>"
    },
    "name": "deployment-killProcess"
  }
}

Input Schema

NameRequiredDescriptionDefault
deploymentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations supply only openWorldHint and idempotentHint; the description adds zero behavioral context. There is no disclosure that a kill is irreversible, what state the deployment ends in, whether permissions or a running process are required, or what errors occur when the process already exited.

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 certainly short, but brevity here reflects under-specification rather than economy: one sentence containing no verb semantics, no scope and no context does not earn its place as a tool description.

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-sounding, open-world mutation with an undocumented required parameter and no output schema, the definition is far too thin. An agent cannot determine what it will destroy, what it returns, or how to recover from calling it.

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

Parameters1/5

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

The single parameter deploymentId has 0% schema description coverage, so the description was the only place to explain what identifier is expected (raw ID vs. name, scope of deployment). It provides none of that.

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 /deployment.killProcess" only restates the tool name in HTTP-route form. It signals a mutating call around a deployment process, but never says what is actually killed (a build process, a running container, a deployment job) or what happens to the deployment afterwards.

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?

No when-to-use, when-not-to-use, or prerequisite guidance at all. With siblings such as application-cancelDeployment, deployment-removeDeployment and docker-killContainer present, the definition offers nothing to help an agent choose between killing a process and canceling or removing a deployment.

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