Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-remove

Destructive

Deletes a server from Dokploy by server ID, enabling cleanup or decommissioning of managed infrastructure.

Instructions

POST /server.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": {
      "serverId": "<serverId>"
    },
    "name": "server-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already state destructiveHint=true and openWorldHint=true, so the safety profile is partially covered by structured data. The description itself adds nothing beyond that: it does not say what state is destroyed, whether the removal cascades to deployments or containers, whether the server must be empty first, or whether the operation is reversible.

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 that brevity is under-specification rather than economy — a verb-plus-path string that conveys no information an agent could not already read from the tool name and schema.

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 destructive, open-world mutation with an undocumented parameter and no output schema, the definition supplies none of the context an agent would need 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.

Parameters2/5

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

Schema description coverage is 0%, so the single required parameter serverId is documented nowhere; the description does not describe its expected format (ID vs. name) or constraints. The only hint is the parameter's name and minLength=1 in the schema.

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 /server.remove" restates the tool name and HTTP verb/resource; the only semantic content is the word "remove" applied to a server. It does not say what removal means (deregistration vs. deletion of the host record vs. data wipe), and it does nothing to distinguish it from siblings like cluster-removeWorker or server-all.

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 alternatives, and no caution about irreversible deletion. An agent must guess entirely from the name.

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