Skip to main content
Glama

network_create

Create a Docker network with specified driver, IPAM, and labels. Supports bridge, overlay, and other scopes for container connectivity.

Instructions

Create a network.

The daemon default driver is bridge (single-host); use overlay for swarm-wide networks. Creating a network attaches nothing — connect containers afterwards with network_connect or at start via container_run(network=...). Created networks are stamped with provenance labels (find them later via network_list(managed_only=True)).

args: name - The name of the network driver - Driver name (daemon default bridge; overlay for swarm scope) options - Driver-specific options dict ipam - IPAM configuration as a dict (engine shape: {"Driver", "Config": [{"Subnet", "Gateway", ...}]}) check_duplicate - Reject creation if a duplicate name exists (deprecated: recent daemons always check) internal - Restrict external access labels - Labels to set on the network enable_ipv6 - Enable IPv6 networking attachable - Allow standalone containers to attach (swarm overlay networks) scope - Network scope: "local", "global", or "swarm" ingress - Make this an ingress network for swarm routing-mesh returns: dict - The created network's attrs (Id, Name, Driver, Scope, IPAM)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipamNo
nameYes
scopeNo
driverNo
labelsNo
ingressNo
optionsNo
internalNo
attachableNo
enable_ipv6No
check_duplicateNo
Behavior4/5

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

Discloses that creation attaches nothing, adds provenance labels, and notes deprecation of check_duplicate. Annotations only mark non-readOnly and non-destructive, so description adds significant behavioral nuance.

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

Conciseness4/5

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

Well-structured with intro and args list. Every sentence adds value, though length could be slightly trimmed without losing clarity.

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, nested objects, and no output schema, the description covers all parameters, explains behavior, and specifies return value, making it complete for agent use.

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?

With 0% schema coverage, the description's 'args' section fully explains all 11 parameters, including types, defaults, and even IPAM shape, adding essential meaning beyond the input schema.

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?

Clearly states 'Create a network.' Differentiates from siblings like network_connect and network_list by specifying that creation attaches nothing and mentioning provenance labels for managed listing.

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?

Provides guidance on default driver (bridge) vs overlay, explains post-creation connection options, and mentions managed_only filtering. Lacks explicit when-not-to-use but context is clear.

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