Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-readTraefikConfig

Read-onlyIdempotent

Read the Traefik configuration from a Dokploy instance to inspect routing and proxy settings before troubleshooting or changing deployments.

Instructions

GET /settings.readTraefikConfig

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond confirming a GET, saying nothing about whether the returned config is the static file, the dynamic provider config, or a computed view, and nothing about failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short token-like string with no filler, so there is nothing to trim. However, its brevity comes from under-specification rather than economy of expression, so it earns only a middling score.

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 zero-parameter read tool with annotations covering safety and no output schema, an agent still needs to know which slice of Traefik configuration is returned, given the dense cluster of similar readers. The description leaves that entirely unanswered, so it is not complete enough to select confidently among siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to clarify about inputs. No credit is lost here even though the description is silent, since the schema is empty and unambiguous.

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 form of the tool name ("GET /settings.readTraefikConfig"), which restates the name rather than explaining what the tool does. It does not say what 'TraefikConfig' contains or how it differs from the many sibling readers such as settings-readMiddlewareTraefikConfig, settings-readWebServerTraefikConfig, and application-readTraefikConfig.

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 mention of prerequisites, and no routing to or away from any of the closely named sibling read tools. An agent has to infer everything from the tool name alone.

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