Skip to main content
Glama
Sign In
Traefik MCP Server

Traefik MCP Server

by gaelhc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_router

Retrieve router details or list routers for HTTP, TCP, or UDP protocols to inspect Traefik configurations.

Instructions

Get information about routers

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

Input Schema

NameRequiredDescriptionDefault
nameNoName of the router including its provider i.e. `name@provider` Returns detailled informations about the router Consult `get_router` without name for list of routers
protocolYesProtocol of the router, 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 supplied, so the description carries the full behavioral burden, yet it only implies a read via the word "Get". It does not state that omitting `name` changes the operation into a list, does not describe the return shape, and says nothing about error behavior for unknown router names.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no waste and nothing buried — structure is clean. The tradeoff is that brevity here reflects under-specification rather than disciplined editing, but there is no filler or redundancy to penalize.

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 annotations and no output schema, the description is the only place behavioral context can come from, and it provides almost none. The list-vs-detail mode switch and the required `protocol` parameter — the two things an agent most needs to get a call right — are entirely absent.

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%, including the `name@provider` format and the protocol enumeration, so the schema already does the parameter work and the baseline of 3 applies. The description adds no parameter meaning of its own, but nothing is missing that the agent needs from 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?

"Get information about routers" names a verb and a resource, so the basic intent is recoverable, but "information" is vague and there is no differentiation from siblings such as get_entrypoint, get_middleware, or get_service. The important distinction between listing routers and fetching one router is only discoverable in the schema, not in the description.

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 or when-not-to-use guidance, no prerequisites, and no pointer to alternatives. The only routing information ("Consult `get_router` without name for list of routers") lives in the parameter schema, not in the description the agent reads first.

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