Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-readWebServerTraefikConfig

Read-onlyIdempotent

Reads the current Traefik web server configuration from Dokploy settings so you can inspect routing and proxy settings before making changes.

Instructions

GET /settings.readWebServerTraefikConfig

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

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. The description adds nothing beyond that - no indication of what the returned config looks like, whether secrets are included, or whether it reflects live vs. persisted state.

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 short and front-loaded by default, but this is under-specification rather than conciseness - the single route string earns its place only as an identifier, not as documentation.

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?

With no parameters and no output schema, the description is the only place an agent could learn what this read returns and how it differs from the nearly identically named Traefik config readers, and it supplies none of that. For a config-reading operation in a crowded namespace, this is a real gap.

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 no parameters, so there is nothing for the description to disambiguate; the empty schema is fully self-explanatory. Baseline 4 applies.

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 'GET /settings.readWebServerTraefikConfig', which restates the tool name rather than explaining what it returns. It conveys that this is a read of the Traefik web-server config at best, but gives no detail on what that config contains or how it differs from the sibling reads (readTraefikConfig, readMiddlewareTraefikConfig, 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 guidance on when to use this tool instead of the many sibling read/update Traefik tools. The description offers no context, prerequisites, or exclusions an agent could act on.

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