Skip to main content
Glama
MCP Dokploy Online
by igoruam

forwardAuth-removeAuthDomain

Destructive

Removes an authentication domain from a Dokploy server's forward auth configuration, helping revoke access tied to that domain.

Instructions

POST /forwardAuth.removeAuthDomain

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>"
    },
    "name": "forwardAuth-removeAuthDomain"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYes

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 already declare destructiveHint=true and openWorldHint=true, so the description would need to add context such as what configuration is lost, whether the change is reversible, or what permissions are required. It adds nothing beyond the endpoint string, leaving the destructive semantics unexplained.

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 that is under-specification rather than conciseness; a bare HTTP route is not front-loaded explanation and earns no informational value for an agent deciding whether to call it.

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?

This is a destructive, open-world mutation with an undocumented required parameter and no output schema. The description supplies none of the surrounding context (target, effect, reversibility, permissions) needed to call it safely.

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?

The single required parameter serverId has 0% schema description coverage, so the description carries the full burden of explaining its meaning. It provides no information at all about what serverId identifies or how it relates to the removed auth domain.

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 /forwardAuth.removeAuthDomain", which restates the tool name rather than stating what the tool does in resource terms. An agent can infer that some ForwardAuth auth domain is removed, but nothing explains what an auth domain is here or what removal implies.

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 the obvious alternatives such as forwardAuth-setAuthDomain or forwardAuth-getAuthDomain. The agent is left to guess 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