Skip to main content
Glama

swarm_init

Initialize a new Docker swarm manager on this Engine, including configuration for network addresses, autolock, and cluster recovery.

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: 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 name - Name of the swarm 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
Behavior5/5

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

Discloses initialization behavior, failure condition, and key behavior about autolock key being shown only once. Annotations already indicate not read-only and not destructive, but description adds valuable context beyond annotations.

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?

Well-structured with a compact paragraph followed by a clean args list. Every sentence adds value; no fluff.

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 11 parameters, zero schema descriptions, and an output schema, the description covers key behaviors, error conditions, and security notes (autolock key). Very complete for a complex initialization tool.

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

Parameters4/5

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

With 0% schema description coverage, description must compensate. It provides explanations for many parameters (advertise_addr, listen_addr, force_new_cluster, etc.), but some (name, labels, log_driver) only listed without additional meaning. Overall helps but not fully exhaustive.

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 explicitly states 'Initialize a new swarm, making this Engine its first manager node.' This is a specific verb and resource, clearly distinguishing it from sibling tools like swarm_join or swarm_leave.

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?

Provides explicit when to use, including failure condition (already part of swarm) and prerequisite (call swarm_leave first). Also advises on next steps (retrieve join tokens, call swarm_join) and when to set advertise_addr. Comprehensive guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/L337-org/docker-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server