Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-getTraefikPorts

Read-onlyIdempotent

Retrieves the configured Traefik ports for a specified Dokploy server, helping you verify proxy port settings and troubleshoot routing or deployment issues.

Instructions

GET /settings.getTraefikPorts

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds nothing beyond that: no indication of which ports are reported, whether a serverId scopes the result, or what happens when it is omitted.

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?

The text is short but that brevity is under-specification rather than economy. It is a bare endpoint path with no front-loaded purpose statement an agent can act on.

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

Completeness1/5

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

Even for a simple read tool with annotations covering safety, the definition leaves the resource meaning, the serverId semantics, and the relationship to sibling Traefik tools entirely unresolved.

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

Parameters1/5

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

The single optional parameter serverId has 0% schema description coverage and the description provides no explanation of its meaning or default behavior. With zero compensation from either source, the agent cannot tell whether omitting it targets the local server.

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 the raw endpoint string 'GET /settings.getTraefikPorts', which essentially restates the tool name. It implies a read of Traefik port settings but never states what is returned or how it differs from siblings like settings-updateTraefikPorts or settings-haveTraefikDashboardPortEnabled.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 prerequisites, and no mention of alternatives. An agent must guess from the name alone whether this is the right tool for inspecting Traefik port configuration.

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