Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-updateTraefikConfig

Idempotent

Updates the Traefik configuration in Dokploy settings to apply routing and proxy changes. Use it when you need to replace the active Traefik config for deployments.

Instructions

POST /settings.updateTraefikConfig

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-updateTraefikConfig"
  }
}

Input Schema

NameRequiredDescriptionDefault
traefikConfigYes

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 idempotentHint=true and openWorldHint=true, so the safety/idempotency profile is covered structurally. The description adds nothing beyond that: it does not say what existing configuration is replaced or destroyed, whether a reload is required, or what permissions/validation apply, which matters for a full-config write on an open-world endpoint.

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 terse with no wasteful wording, but that brevity is under-specification rather than conciseness — one route string carries no front-loaded explanation of purpose or effect.

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 mutation tool that writes an entire Traefik configuration with an undocumented string parameter and no output schema, the definition omits nearly everything an agent needs: expected payload format, overwrite semantics, and post-update effects such as whether Traefik reloads.

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?

Schema description coverage is 0% for the single required parameter traefikConfig, and the description supplies no compensating detail about its expected format (YAML vs JSON), whether it is a full replacement document, or any size/validation constraints beyond minLength=1.

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.updateTraefikConfig", which restates the tool name rather than describing what the update does. It implies an update to some Traefik configuration but does not say whether it replaces the whole config, validates it, or applies it, and gives no basis for distinguishing it from siblings like settings-updateMiddlewareTraefikConfig or settings-updateWebServerTraefikConfig.

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 the read/update/middleware/web-server alternatives that populate the sibling list. The agent must infer usage entirely 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