Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-toggleDashboard

Idempotent

Enable or disable the dashboard for a specific Dokploy server by providing its server ID and the desired on/off state.

Instructions

POST /settings.toggleDashboard

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

Input Schema

NameRequiredDescriptionDefault
serverIdNo
enableDashboardNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations only supply idempotentHint and openWorldHint, leaving the mutation semantics undisclosed. The description does not say whether this changes a live production setting, whether it requires admin auth, or what state results after the call.

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?

A single line with no wasted words, but brevity here is under-specification rather than concision. The route text carries no information an agent could not already derive from the name.

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?

A mutating settings tool with two undocumented parameters, no output schema, and near-empty annotations needs the description to carry the burden, and it carries none of it. The definition is unusable for correct invocation without reading the server source.

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?

Schema description coverage is 0% for two parameters (serverId, enableDashboard), and the description adds no meaning at all. It is unclear whether serverId is required in practice despite the required list being empty, or whether omitting it targets a global default.

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 HTTP route "POST /settings.toggleDashboard", which restates the tool name rather than explaining the operation. It implies a dashboard on/off switch but never says what the dashboard is, what scope the toggle applies to, or which resource is affected.

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 any alternative from the many sibling settings tools. An agent must guess entirely from the name.

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