docker-mcp-server

by L337-org

Overview Schema Source Related Servers Discussions Admin

Python

Local

network_connect

Attach a running container to an additional network without restarting it, giving access to services on that network.

Instructions

Attach a running container to an additional network without restarting it.

Use this to give a container access to services on a network it was not started with. aliases sets extra DNS names for this container within the network (other containers can reach it by those names in addition to its container name). ipv4_address / ipv6_address assign a specific IP on the network; omit to let the driver assign one. links is a legacy feature (deprecated; prefer DNS aliases). Use network_disconnect to undo.

Args: id_or_name: Network id or name to connect the container to container: Container id or name to attach aliases: Additional DNS names for this container within the network links: Legacy container links (deprecated) ipv4_address: Static IPv4 address to assign on this network ipv6_address: Static IPv6 address to assign on this network link_local_ips: Link-local IP addresses to assign driver_opt: Driver-specific endpoint options mac_address: Static MAC address for this endpoint, e.g. "02:42:ac:11:00:04"; per-network rather than per-container, and a driver is free to ignore it

Returns: bool: True after the container is connected

Input Schema

TableJSON Schema

Name	Required	Description	Default
`links`	No
`aliases`	No
`container`	Yes
`driver_opt`	No
`id_or_name`	Yes
`mac_address`	No
`ipv4_address`	No
`ipv6_address`	No
`link_local_ips`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.6Sep 10, 2026
- addedInput schema / properties / mac_address
```
Added value: +{
+  "default": null,
+  "type": "string"
+}
```
Addedv2.0.0Jul 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations indicate a mutating but non-destructive operation, and the description adds useful behavioral details: no restart required, links is deprecated, and mac_address is per-network and may be ignored by the driver. These go beyond the annotation-only safety profile.

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 longer than average but every section earns its place: a clear lead sentence, a usage rationale, structured parameter explanations, and a return note. It remains scannable and front-loaded.

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 9-parameter complexity, the presence of an output schema, and annotations covering the mutation/destructive profile, the description provides all the context needed to invoke the tool correctly, including rollback guidance through network_disconnect.

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 description coverage, the description fully compensates by explaining all 9 parameters, including the meaning of aliases, the deprecation of links, the 'omit to let the driver assign' behavior for IP addresses, and an example for mac_address.

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 opens with a specific verb and resource: 'Attach a running container to an additional network without restarting it.' It clearly distinguishes this from related operations by naming network_disconnect as the undo action.

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?

It explicitly states when to use the tool ('Use this to give a container access to services on a network it was not started with') and directs the user to network_disconnect to undo. It does not enumerate many alternatives, but the key sibling distinction is present.

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

Deploy Server