Skip to main content
Glama
MCP Dokploy Online
by igoruam

network-create

Creates a Docker network in Dokploy with a required name and optional driver, IPAM, MTU, internal, attachable, IPv4/IPv6, and server settings.

Instructions

POST /network.create

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "network-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
mtuNo
ipamNo
nameYes
driverNo
internalNo
serverIdNo
attachableNo
enableIPv4No
enableIPv6No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations supply only a title and openWorldHint=true, leaving the write/destructive profile unstated, so the description carries the full burden. The bare "POST" token hints that this is a mutating, externally visible call, but nothing is said about permissions, side effects on existing networks, or whether the operation is idempotent.

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

Conciseness2/5

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

It is short with no filler, but that brevity comes from under-specification rather than economy; a single route string is not an adequate front-load of information for a 9-parameter mutation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 9 parameters, an enum, a nested ipam object, no output schema, and only minimal annotations, the definition is far too thin for an agent to call this correctly without trial and error.

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

Parameters1/5

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

The schema has 9 parameters at 0% description coverage, and the description explains none of them — not the required name, not the driver enum (bridge/overlay), not the ipam config object, not mtu bounds or the enableIPv4/enableIPv6 flags. An agent must reverse-engineer every field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"POST /network.create" only restates the tool name in HTTP-method form; the resource (a Docker-style network) and the verb (create) are inferable but never stated in plain language. It gives an agent no basis for distinguishing this from siblings such as network-recreate or network-import.

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

Usage Guidelines1/5

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

There is no when-to-use or when-not-to-use guidance at all, no mention of network-recreate/network-import as alternatives, and no prerequisites even though the sibling list is crowded with overlapping create operations.

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

Deploy Server

Other Tools