Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-readTraefikEnv

Read-onlyIdempotent

Retrieves Traefik environment settings for a specified Dokploy server, letting you inspect proxy configuration before making changes.

Instructions

GET /settings.readTraefikEnv

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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 and the description need not repeat it. What the description does not add is any behavioral context beyond the annotations — whether the returned environment may include secrets, whether it reflects the on-disk env file versus a running Traefik instance, or what the openWorldHint means in practice here.

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 short, but short here means under-specified rather than efficient: the single token is a route string with no front-loaded statement of purpose or scope. Every sentence that would earn its place is missing.

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?

There is no output schema, so the description should at least characterize what this read returns, and it does not. Combined with an undocumented parameter and no differentiation from the many sibling read tools, the definition is not sufficient for confident selection or invocation.

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?

There is one optional parameter (serverId) at 0% schema description coverage, and the description says nothing about it. An agent cannot tell whether omitting serverId selects a default node or returns something broader, so the description fails to compensate for the documentation gap.

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 path 'GET /settings.readTraefikEnv', which restates the tool name rather than explaining what it does. It tells an agent it is a read of Traefik environment settings, but never says what an 'environment' here contains (variables? file paths? generated config?), so it cannot be distinguished meaningfully from siblings like settings-readTraefikConfig or settings-readTraefikFile.

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, no prerequisite or permission note, and no pointer to the write counterpart settings-writeTraefikEnv or to the other Traefik read tools. The 'GET' prefix weakly implies a read, but an agent gets no rule for choosing this over the several other Traefik read variants.

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