Skip to main content
Glama

swarm_init

Initialize a new Docker swarm and make this engine the first manager node. Configure advertise address, autolock, and network settings.

Instructions

Initialize a new swarm, making this Engine its first manager node.

Fails if the Engine is already part of a swarm - call swarm_leave first to reset it. advertise_addr only needs setting when the host has multiple network interfaces or is behind NAT (otherwise it is auto-detected); it must be reachable by every other node that will join. To add more nodes afterwards, retrieve join tokens with swarm_join_tokens and call swarm_join on each one. Set autolock_managers=True to require the unlock key (swarm_unlock_key) on every manager restart - store that key securely immediately, since it is only shown once autolock is enabled.

Args: name: Name for the swarm cluster itself, not for the node running init advertise_addr: Externally reachable address advertised to other nodes listen_addr: Listen address used for inter-manager communication force_new_cluster: Force a new single-node cluster from this node's current state (disaster recovery when a majority of managers is lost) default_addr_pool: IP address pools for swarm overlay networks subnet_size: Subnet size for the IP pool data_path_addr: Address to use for data path traffic data_path_port: Port number for data path traffic labels: Labels to set on the swarm autolock_managers: Require the unlock key after every manager restart log_driver: Default log driver configuration

Returns: str: The node id of the newly created swarm manager

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
labelsNo
log_driverNo
listen_addrNo0.0.0.0:2377
subnet_sizeNo
advertise_addrNo
data_path_addrNo
data_path_portNo
autolock_managersNo
default_addr_poolNo
force_new_clusterNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A5/5.0
Behavior5/5

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

Annotations only provide readOnlyHint=false and destructiveHint=false, so the description carries the full burden. It discloses key behaviors: the operation may fail (already in a swarm), certain parameters are conditionally required, autolock_managers triggers the need to store the unlock key immediately, and force_new_cluster is for disaster recovery. This goes well beyond annotations and helps the agent anticipate side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: a clear first sentence, followed by a concise paragraph of usage notes and edge cases, then a clean Args list that is easy to scan. Every sentence adds value; no fluff or repetition. It is appropriately sized for the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the operation's complexity, 11 parameters, no schema descriptions, and an output schema that only specifies a string return, the description covers critical aspects: failure conditions, conditional parameters, security implications, and disaster recovery. It leaves no major gaps for the agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Amid 11 parameters with 0% schema coverage, the description explains the semantics of many: name is for the cluster not the node, advertise_addr is externally reachable and only needed in specific conditions, force_new_cluster is for disaster recovery, and autolock_managers requires immediate key storage. This meaningfully compensates for the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Initialize' and resource 'new swarm', and explains that this Engine becomes the first manager node. It distinguishes this from related operations like swarm_join, swarm_leave, and swarm_join_tokens, and the overall context is unambiguous even among many siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance: it notes failure if already part of a swarm and directs calling swarm_leave first, explains when to set advertise_addr (multi-homed or NAT), and gives a complete workflow for adding nodes via swarm_join_tokens and swarm_join. This is detailed and actionable.

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