Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-updateServer

Idempotent

Update Dokploy server configuration settings via API to adjust instance parameters for deployments.

Instructions

POST /settings.updateServer

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "settings-updateServer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

Annotations only declare openWorldHint=true and idempotentHint=true; they say nothing about whether this mutates state, whether it requires authentication or admin rights, or what happens to existing server settings. With no readOnly/destructive hints, the description carries the full disclosure burden and supplies none of it.

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 is under-specification rather than conciseness: a bare route string with no verb-object statement, no context, and no structure that would help an agent decide or act.

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 zero-parameter mutation-style endpoint with no output schema, the description should at minimum state what is being updated and any preconditions. It provides none of that, leaving the definition inadequate for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

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

The input schema defines zero parameters (additionalProperties: false), so there is no per-parameter meaning for the description to add. The baseline for an empty schema applies despite the description saying nothing about parameters.

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 a restatement of the tool name as an HTTP route: "POST /settings.updateServer". It conveys the transport method but never says in plain language what setting is updated or what the effect is, and the many sibling settings-update* tools make the ambiguity real.

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 guidance on when to use this tool, when not to, or which sibling (settings-updateServerIp, settings-reloadServer, server-update, etc.) is the alternative. The caller must infer everything from the route string alone.

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