Skip to main content
Glama
MCP Dokploy Online
by igoruam

swarm-getNodeInfo

Read-onlyIdempotent

Fetches detailed status and configuration for a Docker Swarm node using its node ID, with optional server targeting for Dokploy infrastructure inspection.

Instructions

GET /swarm.getNodeInfo

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": "swarm-getNodeInfo"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
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 already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered structurally. The description adds nothing beyond them — no note on what swarm node info contains, whether a missing node errors, or what serverId implies for multi-server deployments.

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 with no wasted words, but that brevity reflects under-specification rather than conciseness. There is no front-loaded statement of purpose or behavior to anchor the reader.

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?

With no output schema, no parameter documentation, and an empty description, an agent has essentially nothing beyond annotations and parameter types to call this tool correctly. The definition is inadequate for even a simple lookup.

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 both parameters, and the description provides no compensating meaning. It is unclear whether nodeId is a Docker Swarm node ID or a hostname, and what serverId selects when omitted.

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 endpoint path 'GET /swarm.getNodeInfo', which restates the tool name rather than describing what the tool does. It conveys no more than 'fetch something about a node' and does not distinguish the return payload or scope from siblings like swarm-getNodes.

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 exclusions, and no mention of alternatives such as swarm-getNodes for listing nodes versus fetching a single node's info. The agent must infer the distinction from the name alone.

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