Skip to main content
Glama
MCP Dokploy Online
by igoruam

network-recreate

Recreate a Dokploy network by ID to apply configuration changes or recover from network issues.

Instructions

POST /network.recreate

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-recreate"
  }
}

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 only declare openWorldHint=true, leaving the description to carry the full behavioral burden. A recreate operation is typically destructive and irreversible, yet the description discloses nothing about data loss, required permissions, downtime, or whether existing configuration is preserved.

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 shortness here reflects under-specification rather than economy: a single route token with no verb-object statement, no front-loaded effect, and no actionable content for an agent.

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 mutation tool with one undocumented required parameter, no output schema, and near-empty annotations, the description supplies none of the context an agent needs to invoke it safely. It is effectively a bare endpoint reference.

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 required parameter networkId has 0% schema description coverage, and the description adds nothing about its meaning, format, or where to obtain it. With no other parameters to lean on, the description fully fails to compensate for the schema gap.

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 HTTP route "POST /network.recreate", which restates the tool name in endpoint form. It does not explain what 'recreate' does to a network (destroy and rebuild? re-provision? reset credentials?), so an agent cannot predict the effect.

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 to prefer siblings such as network-remove, network-create, or network-resync. The endpoint string offers no routing logic beyond the word 'recreate'.

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