Skip to main content
Glama
MCP Dokploy Online
by igoruam

whitelabeling-update

Idempotent

Update Dokploy white-labeling settings to change branding assets, links, custom CSS, and error page content for an instance.

Instructions

POST /whitelabeling.update

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": {
      "whitelabelingConfig": "<whitelabelingConfig>"
    },
    "name": "whitelabeling-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
whitelabelingConfigYes

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 supply openWorldHint=true and idempotentHint=true, and the description adds nothing beyond them — no statement about whether the whole config is replaced or merged, whether auth/admin permissions are required, or whether prior values are lost. For an update operation on a nested required object, this is a serious gap.

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?

It is short, but the brevity is under-specification rather than conciseness: a bare route string carries no front-loaded purpose, scope, or constraints. Nothing is wasted, but nearly nothing is conveyed.

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?

Given a mutation tool with a 12-field required nested object, no field descriptions, no output schema, and only two hints from annotations, the definition is nowhere near complete enough to invoke correctly. An agent cannot know what a null value means or whether omitted behavior is possible.

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% and the single parameter is a nested object with twelve required string-or-null properties, none of them described. The description contributes no meaning about any of these fields, so the agent must guess from property names alone.

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 /whitelabeling.update', which restates the tool name rather than describing what the tool does. It hints that whitelabeling configuration is updated, but gives no indication of what fields or effect, and doesn't distinguish it from siblings like whitelabeling-get, whitelabeling-getPublic or whitelabeling-reset.

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 despite siblings such as whitelabeling-reset (which can revert changes) and whitelabeling-get (which reads current values). An agent has nothing to reason about for tool selection beyond 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