Skip to main content
Glama
MCP Dokploy Online
by igoruam

forwardAuth-deployOnServer

Idempotent

Deploy Forward Auth to a Dokploy server by specifying the target server ID and provider ID.

Instructions

POST /forwardAuth.deployOnServer

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

Input Schema

NameRequiredDescriptionDefault
serverIdYes
providerIdYes

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 only supply openWorldHint and idempotentHint; the description adds nothing about what deployment changes on the target server, whether it overwrites existing forward-auth config, what permissions are needed, or what is returned. The POST route weakly implies a mutation, but this is never stated.

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 efficient; a bare route string is not front-loaded explanatory content and carries no actionable information 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?

For a mutating, two-parameter deployment tool with no output schema and minimal annotations, the description omits purpose, prerequisites, effects, and parameter meaning entirely. Nothing an agent needs to invoke it safely is present.

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 there are two required parameters (serverId, providerId) that the description never mentions. No meaning is added for either field, leaving the agent to guess how providerId relates to the forwardAuth provider list.

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.deployOnServer', which restates the tool name rather than explaining what deploying forward auth on a server actually does. It gives no indication of effect, scope, or how it differs from sibling operations like forwardAuth-enable or forwardAuth-removeOnServer.

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 or when-not-to-use guidance, no prerequisites (e.g. that a provider must already exist), and no pointer to alternatives such as forwardAuth-removeOnServer or forwardAuth-serverStatus. The agent must infer everything 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