Skip to main content
Glama
MCP Dokploy Online
by igoruam

forwardAuth-removeOnServer

Destructive

Removes forward authentication configuration from a specified Dokploy server, disabling external auth enforcement for deployments on that server.

Instructions

POST /forwardAuth.removeOnServer

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

Input Schema

NameRequiredDescriptionDefault
serverIdYes

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?

The annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this mutates external state destructively. The description adds nothing beyond the route string: it does not say what configuration is destroyed, whether it can be undone, or what permissions are needed. No contradiction with the annotations, but no added value either.

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 only because it is under-specified rather than because it is efficient. There is no front-loaded statement of purpose and the route string is not meaningful guidance for an agent.

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 destructive mutation with an undocumented required parameter, no output schema, and no annotations explaining blast radius demands far more explanation than is present. The definition supplies essentially none of what an agent needs to invoke 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?

Schema description coverage is 0% and the single required parameter 'serverId' carries no description, type meaning, or format guidance. The description does not compensate at all, leaving the agent to guess what identifier is expected.

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.removeOnServer', which restates the tool name rather than stating in plain language what the tool does. An agent must infer from the name that this removes forward-auth configuration from a server, and it gets no differentiation from siblings such as forwardAuth-removeAuthDomain or forwardAuth-deployOnServer.

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 prerequisite or exclusion information, and no mention of any alternative tool. Nothing tells the agent when removal is appropriate versus disabling or removing an auth domain.

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