Skip to main content
Glama
Sign In
Dokploy MCP Server

Dokploy MCP Server

by bravos2k5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

swarm-getNodeInfo

Read-onlyIdempotent

Retrieve details about a specific node in a Docker swarm by providing the node ID and optional server ID.

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 observedv0.29.1

TDQS

D1.6/5.0
Behavior2/5

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

Annotations indicate readOnlyHint, idempotentHint, and openWorldHint, but the description adds no behavioral context beyond the HTTP method. It does not disclose what data is returned, authentication requirements, or other traits, leaving the agent uninformed about the tool's operation.

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 description is extremely concise but at the expense of clarity. A single line repeating the HTTP endpoint is not well-structured for an agent; it lacks a clear sentence or bullet points that convey purpose in a usable manner.

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 and a sparse description, the tool definition is severely incomplete. The agent cannot determine what information is returned, the structure of the response, or how to interpret the results, making it nearly impossible to use correctly without external knowledge.

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?

The schema has two parameters (nodeId required, serverId optional) with 0% schema description coverage, yet the description provides no explanation of these parameters. The agent cannot infer their meanings or usage from the description alone.

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 merely the HTTP method and endpoint path 'GET /swarm.getNodeInfo', which restates the tool name without explaining what 'node info' entails. It does not use a verb like 'retrieve' or 'get' to clarify the action, and it fails to distinguish from sibling tools 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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools such as 'swarm-getNodes' and 'swarm-getNodeApps' exist, but the description offers no differentiation or context about selecting this tool.

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