Skip to main content
Glama
MCP Dokploy Online
by igoruam

cluster-removeWorker

Destructive

Removes a worker node from a Dokploy cluster using its node ID, optionally scoped to a server ID, to detach the worker from cluster operations.

Instructions

POST /cluster.removeWorker

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": {
      "nodeId": "<nodeId>"
    },
    "name": "cluster-removeWorker"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
serverIdNo

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 already declare destructiveHint=true and openWorldHint=true, so the agent knows this mutates and touches external state. The description adds nothing beyond that — no statement about what is destroyed, whether the node is drained first, or what happens to workloads on the removed worker.

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 is under-specification rather than conciseness: a single HTTP method/path fragment carries no actionable information and is not front-loaded around purpose or effect.

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?

This is a destructive, open-world mutation with two undocumented parameters and no output schema. The description provides none of the operational context (permissions, irreversibility, effect on running workloads) an agent needs before invoking 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?

Schema description coverage is 0% for two parameters (nodeId required, serverId optional), and the description supplies no meaning for either. The agent cannot tell whether nodeId is a cluster node ID or a host identifier, or what serverId does, or why it is optional.

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 raw HTTP route "POST /cluster.removeWorker", which merely restates the tool name (removeWorker on the cluster) in URL form. It names no verb in prose and does not distinguish this from siblings such as cluster-addWorker or server-remove beyond what the identifier already implies.

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 prerequisites, and no mention of an alternative (e.g. removing a manager vs. a worker, or draining first). An agent must guess entirely from the name.

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