Skip to main content
Glama
Sign In
Traefik MCP Server

Traefik MCP Server

by gaelhc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_service

Fetches detailed Traefik service information by name and provider, or lists available services when no name is given; specify the protocol as http, TCP, or UDP.

Instructions

Get information about services

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full discovery burden, yet it discloses nothing about behavior: whether it is read-only, what error occurs for an unknown name, whether protocol must match the service's actual protocol, or what the response contains. 'Get information' leaves an agent guessing about output shape and failure modes.

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?

It is a single short sentence with zero waste, but that brevity comes from under-specification rather than tight editing. Nothing is front-loaded because there is essentially nothing to front-load.

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 lookup tool with no annotations and no output schema, the description should at least characterize what 'information' means and how optional-vs-required parameters change the result. The rich schema partially compensates, but the natural-language definition is too thin relative to the tool's role.

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%, and the name property already explains the `name@provider` format and the list-vs-detail behavior, while protocol documents its allowed values. The description adds no meaning beyond that, so the baseline 3 is appropriate rather than higher.

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 names a verb and resource ('Get information about services'), so the broad purpose is readable, but 'information' is undefined and nothing distinguishes it from siblings like get_router or get_middleware, which follow the same naming pattern. An agent cannot tell what kind of data this returns without opening the schema.

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, no exclusions, and no mention of alternatives in the description. The only routing hint ('Consult `get_service` without name for list of services') lives in the schema's name property, not in the description itself.

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