Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-updateTraefikConfig

Idempotent

Updates the Traefik configuration for a Dokploy application using its application ID and new config, keeping proxy and routing settings aligned with deployment changes.

Instructions

POST /application.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": {
      "applicationId": "<applicationId>",
      "traefikConfig": "<traefikConfig>"
    },
    "name": "application-updateTraefikConfig"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes
traefikConfigYes

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 safety is partially framed, but the description adds no behavior beyond the endpoint string. It does not say that the supplied string likely replaces the whole existing config, what format it expects, whether a Traefik reload is needed, or what permissions are required for a mutation 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?

The single line is short but not concise in the useful sense: it is under-specified rather than economical. There is no front-loaded statement of what changes and no supporting detail, so nothing in the text earns an agent's confidence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a required-parameter mutation tool with no output schema and only weak annotation coverage, the definition is not complete enough to call correctly or safely. The bare route leaves the critical facts about config format, replacement semantics, and post-write effects undocumented.

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% for both required parameters, and the description provides no meaning for either. An agent cannot tell from the definition what applicationId refers to (a name vs. an internal ID) or what shape/structure traefikConfig expects, which is exactly the burden the description should carry here.

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 /application.updateTraefikConfig", which merely restates the tool name's verb and resource. It never says in prose that it replaces the Traefik routing configuration for a specific application, so an agent must infer purpose entirely from the identifier.

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 at all, despite several closely related siblings such as application-readTraefikConfig (the read counterpart) and settings-updateTraefikConfig (a different scope). Nothing indicates whether this overwrites, merges, or applies per-application config, nor when to prefer it over the settings-level variant.

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