Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-updateWebServerTraefikConfig

Idempotent

Updates the Traefik configuration for a Dokploy web server to apply routing, proxy, or middleware changes.

Instructions

POST /settings.updateWebServerTraefikConfig

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": {
      "traefikConfig": "<traefikConfig>"
    },
    "name": "settings-updateWebServerTraefikConfig"
  }
}

Input Schema

NameRequiredDescriptionDefault
traefikConfigYes

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 already declare openWorldHint=true and idempotentHint=true, and the description adds nothing beyond the HTTP method, which is essentially transport detail. It does not state that the call mutates server configuration, whether the prior config is replaced or merged, whether a reload is required, or what permissions are needed — significant gaps for a write tool with no destructiveHint declared.

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 this is under-specification rather than conciseness: the single fragment carries no explanatory content an agent could act on. There is no front-loaded purpose statement beyond the endpoint string.

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 configuration-mutating tool with a free-form string payload, no output schema, and an undocumented parameter, the description supplies none of the context needed to call it safely. An agent would have to guess both the payload format and the effect on existing Traefik settings.

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?

There is one required parameter, traefikConfig, with 0% schema description coverage, and the description says nothing about it. The agent cannot tell whether the string is TOML, YAML, or JSON, whether it replaces or merges existing configuration, or whether it must be a complete file.

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 route "POST /settings.updateWebServerTraefikConfig", which restates the tool name with a verb and a transport. It conveys that a web-server-specific Traefik config is being updated, but only by parsing the identifier itself; it does not distinguish this from closely related siblings such as settings-updateTraefikConfig, settings-updateMiddlewareTraefikConfig, or settings-writeTraefikEnv.

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 tool. Given more than six sibling tools that also update or write Traefik configuration, an agent has no basis for choosing this one over them.

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