Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-updateTraefikPorts

Idempotent

Updates Traefik additional ports for a Dokploy server by setting target, published, and protocol mappings so exposed services route correctly.

Instructions

POST /settings.updateTraefikPorts

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": {
      "additionalPorts": "<additionalPorts>"
    },
    "name": "settings-updateTraefikPorts"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo
additionalPortsYes

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 supply idempotentHint=true and openWorldHint=true, and the absence of readOnlyHint signals mutation, but the description adds nothing beyond the route. It does not say whether existing ports are replaced or merged, whether Traefik restarts or reloads as a side effect, what permissions are required, or whether the change is reversible.

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?

The text is short, but brevity here reflects under-specification rather than concision; the single line is a route stub with no front-loaded purpose statement or usable structure.

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 mutating settings endpoint with a required nested-object parameter, no output schema, and no annotation of readOnly/destructive semantics, the description provides essentially none of the context an agent needs to call it correctly or predict its effect.

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 there are two parameters, including a nested array of objects requiring targetPort, publishedPort, and protocol. The description does not explain serverId (which server's config is targeted) or the structure and semantics of additionalPorts, leaving the agent entirely dependent on field names alone.

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 only restates the HTTP verb and route ("POST /settings.updateTraefikPorts"), which is essentially the tool name reworded. It conveys that this is a write to Traefik port settings but gives no statement of what those settings are or what the update accomplishes, so it cannot be distinguished from sibling mutations like settings-updateTraefikConfig or settings-writeTraefikEnv beyond the route name.

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. An agent cannot tell from the description whether this replaces the whole port list, appends, or how it relates to the read counterpart settings-getTraefikPorts.

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