Skip to main content
Glama
MCP Dokploy Online
by igoruam

forwardAuth-enable

Idempotent

Enables forward authentication for a Dokploy domain using its domain ID, allowing access control to be delegated to an external auth provider.

Instructions

POST /forwardAuth.enable

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": {
      "domainId": "<domainId>"
    },
    "name": "forwardAuth-enable"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations supply openWorldHint and idempotentHint but neither readOnlyHint nor destructiveHint, so the description carries the burden of stating whether this mutates configuration and what it affects. It offers only "POST", which implies mutation but discloses no side effects, permissions, or reversibility. It does not contradict the annotations.

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 text is short but not concise in any useful sense — it is an under-specified endpoint stub with no front-loaded explanation of purpose or effect. Brevity here reflects missing content rather than disciplined editing.

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, domain-scoped enable operation with an undocumented required parameter and no output schema needs a real explanation of preconditions and effects. The description provides none, leaving an agent unable to call it correctly without guessing.

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 the single required parameter domainId, and the description says nothing about it — not whether it is an internal numeric ID or a domain string, nor what happens if it is invalid. With low coverage the description was required to compensate and does not.

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 "POST /forwardAuth.enable", which restates the tool name and HTTP method rather than explaining what enabling ForwardAuth does for a domain. An agent learns nothing about the resource beyond the identifier already present in the name.

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, no prerequisite (e.g., that an auth domain must already be configured), and no reference to the obvious alternative forwardAuth-disable. Usage must be inferred 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