Skip to main content
Glama
MCP Dokploy Online
by igoruam

cluster-addManager

Read-onlyIdempotent

Add a manager to a Dokploy server cluster by specifying the target server ID, assigning cluster administration access for infrastructure and deployment management.

Instructions

GET /cluster.addManager

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds essentially nothing beyond confirming the method is GET — no disclosure of what happens server-side, whether serverId is required in practice, or what an 'add manager' read operation actually returns.

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 only because it is under-specified rather than efficient; the single line is a URL transcription that carries no explanatory content and is not front-loaded with any actionable 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 tool whose name implies adding a cluster manager, an agent needs to know the effect and whether serverId is required; with no annotations explaining semantics, no output schema, and an undocumented parameter, the definition is functionally incomplete.

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?

Schema description coverage is 0% for the single parameter serverId, and the description never mentions it. The schema only supplies the type (string), leaving the agent with no idea what identifier form is expected or whether omitting it changes scope.

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 just the raw HTTP endpoint "GET /cluster.addManager", which restates the tool name rather than explaining what the operation does. An agent learns it is a GET but not what a "manager" is in this context, what it returns, or how it differs from cluster-addWorker.

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 guidance on when to use this tool, no prerequisites, and no mention of alternatives such as cluster-addWorker or cluster-getNodes. The agent must infer everything from the path fragment.

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