Skip to main content
Glama
MCP Dokploy Online
by igoruam

domain-one

Read-onlyIdempotent

Retrieve a specific domain's configuration from Dokploy by its domainId so you can inspect and manage domain settings.

Instructions

GET /domain.one

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

Input Schema

NameRequiredDescriptionDefault
domainIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is supplied elsewhere. The description adds no behavioral context of its own – nothing about not-found handling, scoping, or what the returned domain object contains.

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 concision. A bare HTTP route fragment earns no informational value for an agent deciding how to call the tool.

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?

For a lookup tool with a mandatory identifier and no output schema, the description should at minimum explain the identifier and what comes back. Neither is present, leaving the definition incomplete relative to even this simple tool's needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, domainId, with 0% schema description coverage, and the description says nothing about it. Whether it accepts a numeric ID, a slug, or a hostname is left entirely undocumented.

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?

"GET /domain.one" only restates the tool name with an HTTP verb. It never says what is retrieved (a single domain record? its config? its DNS state?) nor distinguishes it from siblings like domain-byApplicationId or domain-byComposeId.

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 when-to-use guidance at all. An agent cannot tell from this definition whether to call domain-one or domain-byApplicationId/domain-byComposeId for a given lookup.

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