Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-assignDomainServer

Idempotent

Assign a domain and certificate settings to a Dokploy server by configuring the host, HTTPS option, and certificate type, including a Let's Encrypt email when needed.

Instructions

POST /settings.assignDomainServer

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": {
      "host": "<host>",
      "certificateType": "<certificateType>"
    },
    "name": "settings-assignDomainServer"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
httpsNo
certificateTypeYes
letsEncryptEmailNo

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 supply openWorldHint and idempotentHint, but the description adds nothing beyond the verb in the name — no mention of TLS provisioning side effects, restart/reload implications, or whether an existing domain is replaced. For an idempotent but potentially server-affecting operation the description carries none of its share.

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 the brevity is under-specification rather than efficiency; a raw route string is not a front-loaded statement of purpose. There is nothing for the agent to read before deciding 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?

With four parameters, a required enum, no output schema, and no documentation, the definition is far from complete. An agent cannot determine argument semantics or consequences of the mutation from this description.

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 all four parameters (host, https, certificateType, letsEncryptEmail) are undocumented anywhere. The description does not explain the required host format, the meaning of the enum values, or that letsEncryptEmail is presumably required when certificateType is 'letsencrypt'.

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 /settings.assignDomainServer', which merely restates the tool name in endpoint form. It never says what assigning a domain server means — whether it sets the hostname/certificate used for serving requests, or what the effect is on the server.

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?

No when-to-use guidance, no prerequisites, and no mention of any alternative (e.g., settings-updateServer or settings-updateServerIp) despite several plausible siblings. The agent must guess from the name alone.

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