Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-update

Idempotent

Updates an existing Dokploy server's connection and deployment configuration, including its IP address, port, SSH key, server type, and Docker cleanup settings.

Instructions

POST /server.update

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>",
      "description": "<description>",
      "serverId": "<serverId>",
      "ipAddress": "<ipAddress>",
      "port": "<port>",
      "username": "<username>",
      "sshKeyId": "<sshKeyId>",
      "serverType": "<serverType>"
    },
    "name": "server-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
portYes
commandNo
serverIdYes
sshKeyIdYes
usernameYes
ipAddressYes
serverTypeYes
descriptionYes
enableDockerCleanupNo

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 idempotentHint=true and openWorldHint=true but say nothing about the destructive or permission profile of a mutation. The description adds no behavioral context at all — notably it never states that eight parameters are required and therefore that this behaves like a full overwrite of the server record rather than a partial patch.

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 string is short but that brevity is under-specification rather than concision — it spends its single line restating the endpoint and front-loads nothing useful about inputs or effects.

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 ten-parameter, eight-required mutation with no output schema and no annotation coverage of write semantics, this description is completely inadequate. An agent has no basis to construct a correct call or anticipate side effects.

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% across ten parameters, so the description must carry the burden and carries none. Nothing explains name, port, command, sshKeyId nullability, the deploy/build serverType enum, or enableDockerCleanup's default.

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.update" only restates the tool name as an HTTP route. It conveys that a server record is updated, but gives no indication of scope, which fields are affected, or how it differs from siblings such as settings-updateServer or settings-updateServerIp.

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 any alternative. An agent cannot tell from this string whether the call replaces the whole server record or patches a subset, nor when to prefer the settings-* or server-setup variants.

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