Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-readTraefikConfig

Read-onlyIdempotent

Retrieve the Traefik reverse-proxy configuration for a specific Dokploy application. Use it to inspect routing, middleware, and entrypoint rules tied to that app.

Instructions

GET /application.readTraefikConfig

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>"
    },
    "name": "application-readTraefikConfig"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

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?

The annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds nothing beyond them—it does not say what configuration is returned, in what format, or whether the read is scoped to the application's own Traefik overrides versus the global config.

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 that brevity reflects under-specification rather than discipline—the single line is a raw route path with no front-loaded statement of purpose or outcome.

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 tool with one required but undocumented parameter, no output schema, and several near-identical sibling readers, the description does far too little. An agent cannot distinguish this from the settings-level Traefik config readers without guessing from names alone.

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?

Schema description coverage is 0% and the description does not mention applicationId or what form it takes. The parameter name is largely self-explanatory, which prevents a 1, but no meaning beyond the schema is added.

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 /application.readTraefikConfig", which restates the tool name rather than explaining what the tool does. It conveys a read of Traefik configuration scoped to an application, but gives no indication of what part of the config is returned or how this differs from the sibling settings-readTraefikConfig.

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—no statement of when this application-scoped read is preferable to settings-readTraefikConfig or how it relates to application-updateTraefikConfig. The reader is left to infer everything from the endpoint string.

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