Skip to main content
Glama
MCP Dokploy Online
by igoruam

cluster-addWorker

Read-onlyIdempotent

Add a server as a worker node to a Dokploy cluster using its server ID to expand deployment capacity.

Instructions

GET /cluster.addWorker

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": "cluster-addWorker"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, but the description contributes nothing beyond the route string. It does not resolve the tension between an 'addWorker' name (suggesting a mutation) and the read-only hint, nor does it say whether the call is idempotent because the worker already exists or because it only reports state.

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?

The text is short but by omission rather than by efficiency; it is a bare route reference with no front-loaded statement of purpose or effect. Brevity here costs the agent all usable meaning.

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 cluster topology mutation candidate with one undocumented parameter, no output schema, and annotations that conflict with the tool name's implication, the description supplies none of the needed context about effect, prerequisites, or failure behavior.

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 coverage is 0% and there is one parameter (serverId) that the description never mentions. It does not say whether serverId identifies the target cluster, the host to add, or is optional (it is not required), which is exactly the information the schema lacks.

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 "GET /cluster.addWorker", which restates the tool name and adds no human-readable statement of what the operation does (presumably registering a worker node in a cluster). An agent must infer the effect from the name alone, and the sibling names do not disambiguate whether this adds a node, a worker role, or a config entry.

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 reference to alternatives such as cluster-removeWorker or cluster-addManager. An agent has no textual basis for choosing this tool over its 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