Skip to main content
Glama
MCP Dokploy Online
by igoruam

domain-validateDomain

Idempotent

Validates a domain against a Dokploy server to confirm it is properly configured and reachable. Use it to verify domain setup before deploying or troubleshooting routing issues.

Instructions

POST /domain.validateDomain

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

Input Schema

NameRequiredDescriptionDefault
domainYes
serverIdNo

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 declare idempotentHint=true and openWorldHint=true, but the description adds nothing about behavior — whether it performs a DNS lookup, requires serverId for resolution, whether it mutates state, or how failures are surfaced. Given it is an HTTP POST despite being idempotent, some clarification of side effects would be especially valuable, and none is provided.

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 short but that is under-specification rather than conciseness. An HTTP verb and route are not useful information for an agent choosing a tool, so the one sentence present does not earn its place.

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 tool with two undocumented parameters, no output schema, and only weak annotations, the description is completely inadequate. Nothing tells an agent what a successful or failed validation returns or what the call actually does.

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% for two parameters, so the description carries the full burden and provides none. It never explains what 'domain' should look like (bare name vs. FQDN), whether 'serverId' scopes the check to a specific server, or which combinations are valid.

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.validateDomain', which restates the tool name rather than stating what validation means, what it checks, or what a result signifies. An agent learns nothing beyond 'this touches a domain' and cannot distinguish it from siblings like server-validate or licenseKey-validate.

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 or when not to use it. With siblings such as domain-one, domain-create, and domain-update present, the agent is left to guess why or when to call validateDomain.

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