Skip to main content
Glama
MCP Dokploy Online
by igoruam

forwardAuth-setAuthDomain

Idempotent

Configure forward authentication for a Dokploy server by setting its auth domain and HTTPS certificate options.

Instructions

POST /forwardAuth.setAuthDomain

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": {
      "serverId": "<serverId>",
      "authDomain": "<authDomain>"
    },
    "name": "forwardAuth-setAuthDomain"
  }
}

Input Schema

NameRequiredDescriptionDefault
httpsNo
serverIdYes
authDomainYes
certificateTypeNoletsencrypt
customCertResolverNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true and openWorldHint=true, so the baseline is lowered, but the description contributes nothing beyond them: no statement about what configuration is overwritten, whether a Traefik restart/redeploy follows, or what certificate implications exist. The only hint of behavior is the bare HTTP verb POST, which is fully implied by the name.

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?

The single string is short but is under-specification rather than conciseness; there is no front-loaded statement of intent and no structure to scan. Nothing in it earns its place as documentation.

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?

For a five-parameter, enum-bearing mutation tool with no output schema and zero schema descriptions, the definition omits everything an agent needs: effect of the call, idempotency consequences, certificate side effects, and parameter documentation. It is not usable as a standalone basis for correct invocation.

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% across five parameters, including the required serverId and authDomain plus the enum-backed certificateType and customCertResolver. The description must compensate entirely and instead supplies no semantic meaning for any parameter, leaving the agent to guess at relationships such as whether customCertResolver only applies when certificateType is 'custom'.

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 nothing more than the route string "POST /forwardAuth.setAuthDomain", which restates the tool name rather than explaining what an auth domain is, what setting it accomplishes, or how it differs from siblings such as forwardAuth-getAuthDomain or forwardAuth-removeAuthDomain. An agent learns no verb-plus-resource meaning beyond the name itself.

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 (getAuthDomain, removeAuthDomain, deployOnServer) that plausibly compete for the same request. The agent must infer selection purely from sibling naming.

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