Skip to main content
Glama
MCP Dokploy Online
by igoruam

domain-canGenerateTraefikMeDomains

Read-onlyIdempotent

Checks whether a specified Dokploy server can generate Traefik.me domains, helping you confirm domain availability before configuring deployments.

Instructions

GET /domain.canGenerateTraefikMeDomains

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

Input Schema

NameRequiredDescriptionDefault
serverIdYes

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?

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, and the GET wording is consistent with them, so there is no contradiction. However, the description adds nothing beyond those structured hints — no indication of what is checked, what authorization or serverId preconditions apply, or what the boolean-ish result means.

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 that brevity comes from under-specification rather than efficiency; a bare endpoint path is not a meaningful front-loaded summary of intent.

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 no output schema, one undocumented required parameter, and no explanation of the capability check, the definition leaves an agent unable to determine what the tool returns or when calling it is meaningful. Nothing beyond the route string is supplied.

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?

There is a single required parameter (serverId) with 0% schema description coverage, and the description says nothing about it — not its format, whether it is an internal identifier, or how it scopes the domain check. The description therefore fails to compensate for the documentation gap.

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 only restates the tool name as a raw HTTP route ("GET /domain.canGenerateTraefikMeDomains"). It gives no plain-language statement of what the check does, what 'Traefik Me domains' are, or why an agent would call it, so the purpose is inferable only from the name itself.

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 how this differs from siblings such as domain-generateDomain, domain-validateDomain, or domain-one. The agent must guess the selection criteria entirely.

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