Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-readMiddlewareTraefikConfig

Read-onlyIdempotent

Retrieves the Traefik middleware configuration from Dokploy settings to inspect routing and middleware rules for deployment troubleshooting.

Instructions

GET /settings.readMiddlewareTraefikConfig

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already state readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered by structured data. The description contributes no additional behavior beyond the annotations — nothing about whether middleware config is merged from multiple sources, whether it touches the live Traefik instance, or what failure modes exist for an open-world read.

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 a single short line with no waste, but brevity here comes from under-specification rather than economy — the whole description is a route string that duplicates the name. There is no front-loaded statement of what is returned or when to call it.

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 output schema and no explanatory text, an agent cannot know what shape or scope of middleware configuration comes back (e.g., single middleware vs. full entrypoint config). For an open-world read against live Traefik settings, the definition should supply at least that much context.

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, so the schema is complete and self-explanatory; a baseline of 4 applies. The description does not need to explain inputs and correctly does not attempt to.

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 raw route label 'GET /settings.readMiddlewareTraefikConfig', which restates the tool name and HTTP verb without saying what the middleware Traefik configuration actually is or how it differs from settings-readTraefikConfig or settings-readWebServerTraefikConfig. An agent could infer 'read the middleware Traefik config' from the name alone, so the text adds essentially nothing.

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?

No when-to-use, when-not-to-use, or prerequisite information is given, despite several closely related siblings (readTraefikConfig, readWebServerTraefikConfig, updateMiddlewareTraefikConfig) that a reader would need to disambiguate against. The verb 'GET' hints at a retrieval operation but provides no routing guidance.

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