Skip to main content
Glama
MCP Dokploy Online
by igoruam

domain-generateDomain

Idempotent

Generates a domain configuration for a specified application in Dokploy, optionally targeting a server. Use it to create the domain entry needed before attaching a hostname to your app.

Instructions

POST /domain.generateDomain

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": {
      "appName": "<appName>"
    },
    "name": "domain-generateDomain"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNameYes
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations declare openWorldHint=true and idempotentHint=true, so the agent knows the call is externally visible and repeat-safe. The description adds nothing about what is actually created, whether it is destructive or reversible, what permissions are needed, or what the response contains — a meaningful gap for a mutation-style operation.

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 single line is technically concise and front-loaded with the HTTP verb, but this is under-specification rather than conciseness. Restating the route consumes the entire budget without conveying actionable meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has two undocumented parameters, one required, no output schema, and only partial annotations. For that complexity the description should at minimum state what a 'generated domain' is and how serverId affects the outcome; it does none of that while still implying an external side effect.

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%, so the description carries the full burden for both parameters and supplies none. It never explains what appName identifies, how serverId interacts with it, or whether serverId is optional with a default.

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 /domain.generateDomain', which restates the tool name and title rather than explaining what generating a domain means. An agent cannot tell from this whether the tool provisions a DNS record, mints a certificate, or assigns a Traefik-managed domain, nor how it differs from siblings such as domain-create or domain-canGenerateTraefikMeDomains.

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 preconditions, and no mention of alternatives. The vehicle is the schema only; the description offers nothing to route an agent between this tool and domain-create or the Traefik domain checks.

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