Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-updateRemoteServersOnly

Idempotent

Updates the Dokploy setting that controls whether only remote servers are used, so you can restrict deployment and infrastructure operations to remote servers.

Instructions

POST /settings.updateRemoteServersOnly

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": {
      "remoteServersOnly": "<remoteServersOnly>"
    },
    "name": "settings-updateRemoteServersOnly"
  }
}

Input Schema

NameRequiredDescriptionDefault
remoteServersOnlyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond the endpoint string: it does not say whether the change is reversible, what existing configuration it affects, or what permissions are required for a global settings mutation.

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 short through under-specification rather than economy; the endpoint string adds no information an agent did not already have from the tool name. Nothing is front-loaded because there is no explanatory content.

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 global-settings mutation with an undocumented boolean parameter and no output schema, the definition supplies none of the context an agent needs to act safely. The only structured hints are the annotations, which do not explain what the flag does.

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?

The single required parameter remoteServersOnly has 0% schema description coverage, so the burden falls on the description, which says nothing about the flag's meaning or consequences. The only signal is the boolean type and the parameter's name.

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 endpoint string "POST /settings.updateRemoteServersOnly", which restates the tool name rather than explaining the operation. An agent learns that a settings field named remoteServersOnly is being mutated, but not what that flag controls or what effect toggling it has.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 how this differs from siblings such as settings-updateServer or the other settings-update* tools. The agent must infer usage 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