Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-updateServerIp

Idempotent

Updates the configured server IP address for a Dokploy instance using the required serverIp value.

Instructions

POST /settings.updateServerIp

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": {
      "serverIp": "<serverIp>"
    },
    "name": "settings-updateServerIp"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIpYes

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 declare openWorldHint=true and idempotentHint=true, so part of the behavioral profile is covered. The description adds nothing further, such as whether the change requires a restart, whether the IP is the public server address, or what happens to existing connections.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a one-line string with nothing superfluous, and the endpoint is front-loaded. But the brevity comes from under-specification rather than efficiency.

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 settings mutation affecting server networking, the definition omits input format, side effects and safety implications. Even with annotations covering safety hints, an agent cannot call this correctly without guessing.

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% and the single required parameter, serverIp, is documented nowhere. The description does not say what format the IP should take (IPv4, CIDR, hostname) or whether it must be a public address.

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 just "POST /settings.updateServerIp", which restates the tool name and adds only the HTTP method. It never explains what updating the server IP means or how it differs from siblings such as settings-updateServer or settings-getIp.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives like settings-updateServer or settings-updateWebServerTraefikConfig. The agent has to infer everything from the tool 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