Skip to main content
Glama
MCP Dokploy Online
by igoruam

whitelabeling-get

Read-onlyIdempotent

Fetches the whitelabeling configuration from your Dokploy instance, letting you review current branding settings before applying changes.

Instructions

GET /whitelabeling.get

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": "whitelabeling-get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 by structured fields. The description adds nothing beyond them: no note on authentication/tenant scoping, no indication of what configuration is returned, and no caveats about the external network reach implied by openWorldHint.

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 shortness here reflects under-specification rather than economy. A route stub is not a useful description, and there is no front-loaded statement of purpose or return content.

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?

With no output schema, the description is the only place an agent could learn what this returns, and it says nothing. For a zero-argument read against an external system, one sentence about the returned whitelabeling configuration would have made this callable with confidence.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The empty schema and additionalProperties:false mean an agent can call it without parameter risk.

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?

"GET /whitelabeling.get" merely restates the tool name and title with an HTTP verb bolted on. It conveys that this is a read of whitelabeling configuration, but nothing about what aspect of whitelabeling (branding assets? domain settings? feature flags?) or how it differs from the sibling whitelabeling-getPublic.

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 at all. The existence of a sibling named whitelabeling-getPublic strongly implies a public/private split, but the description never states which one an agent should pick or under what conditions, leaving the choice to guesswork.

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