Skip to main content
Glama
MCP Dokploy Online
by igoruam

network-remove

Destructive

Deletes a specified Docker network in Dokploy by network ID to clean up unused or obsolete networks.

Instructions

POST /network.remove

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": {
      "networkId": "<networkId>"
    },
    "name": "network-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkIdYes

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 flag destructiveHint=true and openWorldHint=true, so the safety profile is known, but the description adds zero context beyond that — not what gets destroyed, whether removal fails when the network is in use, or whether it is reversible. For an irreversible mutation the description should carry more, not less.

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?

The text is short but that is under-specification rather than concision; a bare HTTP route is not a useful front-loaded statement of intent. Nothing here is wasted because there is essentially nothing here.

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?

A destructive, single-parameter tool with no output schema needs the description to state the effect, the identifier format, and the failure modes. None of those are present, so the definition is inadequate for an agent to call it safely or correctly.

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 single parameter networkId has 0% schema description coverage, so the description is the only place meaning could be supplied, and it supplies none. It does not say whether the value is an ID, a name, or a slug, nor what happens if the identifier does not exist.

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?

The description is only the raw HTTP endpoint "POST /network.remove", which merely restates the resource already conveyed by the tool name. It gives no verb describing the effect (delete? detach?) or scope, so an agent must infer that this removes a network rather than modifying or detaching it. Sibling names like network-one and network-inspect are not differentiated in any way.

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, no mention of what happens to attached containers/services, and no pointer to alternatives such as network-inspect or network-recreate. The description offers nothing an agent could use to decide whether this is the right call.

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