Skip to main content
Glama
MCP Dokploy Online
by igoruam

domain-create

Creates a domain mapping for a Dokploy application, compose service, or preview deployment, with options for host, path, port, HTTPS, and certificate settings.

Instructions

POST /domain.create

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>"
    },
    "name": "domain-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
pathNo
portNo
httpsNo
composeIdNo
stripPathNo
domainTypeNo
middlewaresNo
serviceNameNo
internalPathNo
applicationIdNo
certificateTypeNo
customEntrypointNo
customCertResolverNo
forwardAuthEnabledNo
previewDeploymentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations supply only openWorldHint=true and a title; there is no destructive or readOnly hint. For a mutation that creates a domain routing entry (potentially affecting live traffic, TLS, and Traefik config), the description discloses nothing about side effects, required permissions, whether creation is idempotent, or what happens on conflicts with an existing host.

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 brevity reflects under-specification rather than economy; a bare route string has no front-loaded explanation of purpose, effect, or parameters. There is nothing to trim because nothing of substance was written.

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 16-parameter creation tool with no output schema, no meaningful annotations, and 0% parameter documentation needs a substantive description to be callable correctly. The supplied one-paragraph route string leaves the agent with no information on required combinations (e.g., composeId vs applicationId vs domainType) or certificate handling.

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% across 16 parameters, so the description carries the full explanatory burden and provides none of it. Fields like stripPath, certificateType, customEntrypoint, forwardAuthEnabled, and middlewares are entirely undocumented in both schema and description.

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 essentially the HTTP route "POST /domain.create", which restates the tool name and title rather than explaining what the tool does. An agent can infer that a domain record is created, but nothing about scope, target, or effect is stated beyond the verb implied by the route.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus siblings such as domain-update, domain-generateDomain, or domain-validateDomain. The only implicit signal is the POST/create framing, which an agent must infer from the route string rather than from stated instructions.

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