Skip to main content
Glama
Sign In
Traefik MCP Server

Traefik MCP Server

by gaelhc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_middleware

Retrieve detailed information about a Traefik middleware by name and protocol, or omit the name to list available middlewares. Use it to inspect HTTP, TCP, or UDP middleware configuration.

Instructions

Get information about middlewares

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": {
      "protocol": "<protocol>"
    },
    "name": "get_middleware"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName of the middleware including its provider i.e. `name@provider` Returns detailled informations about the middleware Consult `get_service` without name for list of middlewares
protocolYesProtocol of the middleware, in ['http', 'tcp', 'udp']

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only lookup, what happens when the middleware name is unknown, whether protocol must match the middleware's actual protocol, or anything about the response shape.

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?

One short sentence, front-loaded and free of filler, but the brevity comes from omission rather than efficiency — there is no second sentence carrying scope, alternatives, or return-value context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (two documented params, no output schema, no annotations), so the schema's rich parameter text covers most of what an agent needs to invoke it. The description itself contributes nearly nothing, leaving discovery of the list-vs-detail distinction to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters (name with `name@provider` format, protocol enum-ish list) are already fully documented in the schema. The description adds no meaning beyond that, which meets the baseline of 3 rather than exceeding it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a generic verb+resource ("Get information about middlewares"), so an agent knows it is a read of middleware data, but not what kind of information (config, status, providers) or how it differs from siblings like get_service or get_router beyond the name. It is specific enough to act on only because the schema names the lookup keys.

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?

The description gives no when-to-use, when-not-to-use, or alternative-tool guidance. The useful routing hint ("Consult `get_service` without name for list of middlewares") lives only in the schema's parameter text, not in the description.

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