Skip to main content
Glama

network_create

Create a Docker network with a specified driver, IPAM, and labels. Define bridge or overlay networks, restrict external access, or enable IPv6 for isolated container communication.

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; the driver picks a sensible default when omitted 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?

Beyond the minimal annotations (readOnlyHint=false, destructiveHint=false), the description adds notable behavioral context: creation attaches nothing, provenance labels are stamped, and check_duplicate behavior is noted. It doesn't mention permissions or error cases but covers key traits.

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 one-line summary, key behavioral notes, and a clear arg list. Every sentence provides value, and the length is appropriate for the parameter count. No fluff or redundancy.

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?

Despite high complexity (11 params, nested objects, no output schema), the description covers usage, parameter meanings, return format (dict with attrs), and ties to related tools. It is sufficiently complete for an agent to invoke correctly without external documentation.

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?

Schema has 0% description coverage, so the description fully compensates by explaining each of the 11 parameters, including IPAM shape, driver defaults, and special flags like ingress and attachable. This adds significant meaning beyond the raw schema types.

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 'Create a network' with the resource and action. It differentiates from sibling tools like network_connect and network_disconnect by focusing on creation. The addition of daemon default driver and overlay usage clarifies scope.

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?

Explicitly provides when to use (for swarm-wide networks use overlay), how to connect containers afterward via network_connect or container_run, and how to find created networks via network_list(managed_only=True). This distinguishes it from alternatives and gives clear usage context.

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