Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-reloadTraefik

Idempotent

Reload Traefik configuration on a Dokploy server to apply updated proxy or routing settings.

Instructions

POST /settings.reloadTraefik

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo

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 supply openWorldHint=true and idempotentHint=true, so the safety profile is partially covered, but the description adds nothing about what a reload entails — whether it restarts the proxy, causes downtime, validates config first, or requires elevated permissions. For a potentially service-affecting operation, this is a substantial gap, though it does not contradict the idempotent hint.

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 a single short line, so nothing is wasted, but that brevity comes from under-specification rather than efficiency. The only content is a route string that duplicates the tool name instead of front-loading useful intent.

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?

With no output schema, no parameter documentation, and a mutation-style operation, the description should carry the full burden of explaining effect and side effects. Instead it supplies a bare endpoint, leaving an agent unable to judge consequences or parameter meaning.

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% and the single parameter 'serverId' is neither documented in the schema nor explained in the description. The agent cannot tell whether serverId scopes the reload to one node or is optional because it defaults to all servers, and no format or default value is given.

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 raw route 'POST /settings.reloadTraefik', which restates the tool name rather than explaining what reloading Traefik actually does. An agent can infer a mutation of Traefik settings, but nothing distinguishes it from siblings like settings-reloadServer or settings-updateTraefikConfig beyond the literal route string.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as settings-updateTraefikConfig or settings-readTraefikConfig. The verb 'reload' implies a runtime refresh, but the agent must guess at the trigger conditions.

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