Skip to main content
Glama

stack_deploy

Deploy or update a Docker stack to a swarm from Compose files, with options for detach, prune, registry auth, and image resolution.

Instructions

Deploy (or update) a stack to the swarm from one or more Compose files.

Requires the target daemon to be a swarm manager. Re-running with the same stack_name updates the stack in place. Defaults to detach=True (returns once specs are submitted, not on convergence); set detach=False to wait for the rollout (give it a generous timeout_seconds).

args: stack_name - Name of the stack to create or update compose_files - One or more Compose file paths (repeated -c; later override earlier). At least one required. with_registry_auth - Send registry credentials to swarm agents (needed for private images) prune - Remove services no longer defined in the Compose file resolve_image - Image-digest resolution: "always" (default), "changed", or "never" detach - Return immediately after submitting specs (True) vs wait for convergence (False) cwd - Working directory for resolving relative Compose paths (defaults to the server's cwd) timeout_seconds - Subprocess timeout (default 1800s) returns: dict - {"returncode": int, "stdout": str, "stderr": str, "truncated": bool}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNo
pruneNo
detachNo
stack_nameYes
compose_filesYes
resolve_imageNo
timeout_secondsNo
with_registry_authNo
Behavior4/5

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

Annotations indicate mutating behavior (readOnlyHint=false) and not explicitly destructive (destructiveHint=false). The description adds important behavioral details: default detach=True behavior, the effect of prune flag, and the need for registry_auth for private images. This goes beyond annotations but does not cover all edge cases like rollback behavior.

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 one-sentence purpose, followed by prerequisites and behavioral notes, then a bullet list of parameters. Every sentence adds value, no redundancy. It is concise yet comprehensive.

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 complexity of the tool (8 parameters, swarm deployment), the description covers prerequisites, parameter details, return format, and key behaviors like detach default. It provides all necessary information for an AI agent to correctly invoke the tool without needing an output schema.

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?

The description fully compensates for 0% schema description coverage by listing all 8 parameters with clear explanations, defaults, and behavior. It explains each parameter's role (e.g., stack_name, compose_files, prune, detach). The return value is also described. This is thorough and leaves no ambiguity.

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 'Deploy (or update) a stack to the swarm from one or more Compose files,' which specifies the exact action (verb: deploy/update) and resource (stack). It distinguishes from sibling tools like stack_ls or stack_rm by explaining that this creates or updates stacks.

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

Usage Guidelines4/5

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

The description provides prerequisites (daemon must be a swarm manager) and explains re-running updates the stack in place, giving clear context. However, it does not explicitly state when to avoid using this tool or mention alternative tools for related tasks (e.g., stack_ls for listing).

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/GavinLucas/docker-mcp'

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