Skip to main content
Glama
MCP Dokploy Online
by igoruam

swarm-getNodes

Read-onlyIdempotent

Retrieve the nodes in a Docker Swarm cluster for a specified Dokploy server to inspect node status and capacity.

Instructions

GET /swarm.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": "swarm-getNodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 readOnlyHint, idempotentHint and openWorldHint, and the description contributes nothing beyond them — no statement of return shape, pagination, error behavior, or what 'nodes' means in swarm context. It is a bare endpoint echo, adding zero behavioral context.

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 this is under-specification rather than conciseness — a single URL fragment that earns no informational place. There is no front-loaded verb or scope for an agent to anchor on.

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 read tool with an optional filter parameter, no output schema, and ambiguous siblings, the description supplies nothing an agent needs. It is not complete in any meaningful sense.

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 the single `serverId` parameter, and the description does not mention it at all. With one undocumented optional parameter, the description fully fails to compensate for the schema gap; there is no hint whether omitting serverId queries all servers or a default.

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 /swarm.getNodes", which merely restates the tool name in HTTP form. It implies a retrieval of swarm node data but gives no scope, no statement of what a node record contains, and no differentiation from sibling tools like cluster-getNodes or swarm-getNodeInfo.

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 whatsoever about when to use this tool versus the closely named siblings (cluster-getNodes, swarm-getNodeInfo, swarm-getNodeApps). The agent must infer from the name alone whether this lists all swarm nodes or does something else.

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