Skip to main content
Glama
MCP Dokploy Online
by igoruam

forwardAuth-disable

Idempotent

Disables forward authentication for a specified Dokploy domain using its domain ID.

Instructions

POST /forwardAuth.disable

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

Input Schema

NameRequiredDescriptionDefault
domainIdYes

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 supply openWorldHint=true and idempotentHint=true, and the description adds nothing on top of that. The bare "POST" at least confirms a mutating HTTP call, but the description does not say whether existing auth-domain configuration is preserved or destroyed, what permissions are required, or what happens on repeat calls.

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 this is under-specification rather than conciseness: a single route string with no front-loaded statement of effect or scope. Nothing in the one line helps an agent decide or prepare a call.

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 mutating tool with no output schema, no destructive or permission annotations, and an undocumented required identifier, the definition is far too thin. It should at minimum explain the effect of disabling, reversibility, and what domainId identifies.

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 domainId has 0% schema description coverage, and the description does not mention it at all. There is no hint about what a domainId refers to (an auth domain entity vs. a DNS domain), its format, or how to obtain one.

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.disable", which merely restates the tool name in method+path form. It conveys no verb+resource explanation of what disabling ForwardAuth actually does (e.g., turning off an auth gate for a domain) or how that differs from siblings like forwardAuth-enable or forwardAuth-removeAuthDomain.

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 anywhere in the definition. An agent cannot tell from this text whether to call disable versus removeAuthDomain or removeOnServer when it wants to stop ForwardAuth.

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