Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-readTraefikFile

Read-onlyIdempotent

Reads a Traefik configuration file from a Dokploy server by path, so you can inspect proxy routing and settings.

Instructions

GET /settings.readTraefikFile

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": {
      "path": "<path>"
    },
    "name": "settings-readTraefikFile"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 by structured data. The description adds nothing beyond that — no mention of what is returned, whether arbitrary paths are restricted to a Traefik config root, or how missing files are reported.

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 the brevity reflects under-specification rather than economy. A bare route string is not front-loaded information an agent can act on.

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?

A file-reading tool with no output schema, no documented parameters and no annotation-independent explanation leaves the agent guessing about return shape and path constraints. The annotations cover safety, but nothing else is filled in.

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 two parameters, so the description carries the full burden and supplies nothing. It never explains what 'path' is relative to, whether it is absolute, or what 'serverId' selects when omitted.

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 just the HTTP route 'GET /settings.readTraefikFile', which restates the tool name rather than explaining what it does. It implies reading a Traefik configuration file but never states it in plain terms, and gives no hint of how it differs from sibling reads like settings-readTraefikConfig or settings-readTraefikEnv.

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, when not to, or which sibling to choose instead. An agent facing seven near-identical read*Traefik* tools has nothing to disambiguate them.

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