Skip to main content
Glama
MCP Dokploy Online
by igoruam

cluster-getNodes

Read-onlyIdempotent

Retrieve the nodes in a Dokploy cluster to inspect server infrastructure. Optionally filter by server ID for targeted cluster monitoring and management.

Instructions

GET /cluster.getNodes

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/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 nothing beyond that — no note about what is returned, whether results are cluster-wide, or whether serverId scoping matters, which is exactly the context an agent would need here.

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 brevity here is under-specification rather than economy: the single line is a route string that conveys no task-relevant information. There is nothing to be front-loaded because no content exists.

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-inspection tool with no output schema and an undocumented optional parameter, the definition provides none of the information an agent needs to invoke it confidently. Nothing explains the return shape, scope, or behavior.

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?

There is one optional parameter (serverId) with 0% schema description coverage, and the description does not explain what it selects or what happens if it is omitted. With no parameter documentation anywhere, the definition fails to compensate for the schema gap.

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 the raw endpoint string "GET /cluster.getNodes", which merely restates the tool name in HTTP form. It does not say what a "node" is in this cluster context (manager/worker, host, container) or what the response contains, leaving an agent to infer meaning from the name alone.

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 mention of prerequisites or authentication, and no differentiation from the similarly named sibling swarm-getNodes. Usage can only be guessed from the tool 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