Skip to main content
Glama
MCP Dokploy Online
by igoruam

whitelabeling-getPublic

Read-onlyIdempotent

Fetch the public whitelabeling configuration for a Dokploy instance so clients can display branding without requiring authentication.

Instructions

GET /whitelabeling.getPublic

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds nothing beyond those annotations – not whether the call is unauthenticated, what scope of settings is exposed, or any rate/latency considerations. No contradiction exists, but there is no added value.

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?

The text is a single terse route string with no wasted words, but it is under-specified rather than truly concise. It is front-loaded only in the trivial sense that there is nothing else.

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 zero parameters and no output schema, the description is the sole channel for explaining what this endpoint returns and whether it requires authentication – and it supplies neither. For a public-facing whitelabeling read, that leaves an agent guessing about the return payload and access model.

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 there is no parameter meaning to convey. Baseline 4 applies; the description could not add parameter detail even if it wanted to.

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 'GET /whitelabeling.getPublic', which restates the tool name and HTTP route rather than describing the resource being fetched. An agent can infer it retrieves public whitelabeling settings, but that inference comes from the name, not the description.

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 explicit when-to-use guidance, no prerequisites, and no differentiation from the sibling 'whitelabeling-get'. The word 'getPublic' faintly implies the unauthenticated/public variant, but that is inference rather than stated guidance.

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