Skip to main content
Glama
MCP Dokploy Online
by igoruam

network-import

Idempotent

Import existing Docker networks by name into Dokploy, optionally scoped to a specific server, so deployments can reuse them.

Instructions

POST /network.import

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": {
      "names": "<names>"
    },
    "name": "network-import"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already state openWorldHint=true and idempotentHint=true, so the bar is lower, but the description adds nothing: no statement of side effects, whether existing networks are overwritten or merged, what auth is required, or what happens on partial failure. An import that may mutate state deserves at least a hint about its effect.

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, but short because it is empty rather than because it is efficient; the single token string encodes no information an agent can act on. There is no front-loaded statement of purpose or constraints.

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?

For a tool with two parameters, one required array, zero schema description coverage, and no output schema, the description should explain both inputs and the resulting effect. None of that is present, so an agent has nothing to work with beyond the raw schema types.

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?

Schema description coverage is 0%, so the description must carry the meaning of parameters, yet it says nothing about either one. The required 'names' array and the optional 'serverId' are entirely unexplained — their format, whether names refer to existing networks or new ones, or what serverId scopes.

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.import" only restates the tool name as an HTTP endpoint; it never says what an import does (bring networks in from an external source? from a file? from a prior export?). It gives no way to distinguish this from siblings like compose-import, network-create, or network-recreate.

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 guidance, no prerequisites, and no mention of when a different sibling (e.g. network-create or compose-import) would be the right choice. The endpoint string conveys nothing about the conditions that select this tool.

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