Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-haveTraefikDashboardPortEnabled

Read-onlyIdempotent

Checks whether the Traefik dashboard port is enabled on a specified Dokploy server, so you can confirm the dashboard is exposed before accessing or troubleshooting it.

Instructions

GET /settings.haveTraefikDashboardPortEnabled

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/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 structurally. The description adds nothing beyond that: no indication of what a true/false result means operationally, whether the check requires a running Traefik instance, or what happens when serverId 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.

Conciseness3/5

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

It is a single short route string with no wasted wording, so it is concise, but the brevity reflects under-specification rather than front-loaded clarity. There is no sentence structure or hierarchy directing an agent to relevant context.

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?

There is no output schema and no annotation-level explanation of the boolean result, so the description must carry the semantic burden — and it does not. For a check-style tool with an optional serverId and no documentation of scope or return meaning, the definition is insufficient to invoke it confidently.

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

Parameters2/5

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

Schema description coverage is 0% for the single serverId parameter, and the description does nothing to compensate — it never mentions serverId, its meaning, its default when omitted (it is optional), or which server it scopes the check to. With only one parameter and no explanatory text, the agent is left guessing.

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 only the raw route string 'GET /settings.haveTraefikDashboardPortEnabled', which restates the tool name rather than explaining what the check does. An agent can guess it reports whether the Traefik dashboard port is enabled, but the definition never states that in plain terms or distinguishes it from siblings like settings-haveActivateRequests.

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?

No when-to-use guidance, no prerequisites, and no mention of the related sibling settings-toggleDashboard, which is the obvious action counterpart. The route string gives no context signal for selection.

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