Skip to main content
Glama
MCP Dokploy Online
by igoruam

domain-toggleEnable

Idempotent

Toggles the enabled state of a Dokploy domain by its domainId, letting you activate or deactivate a domain through the API without deleting its configuration.

Instructions

POST /domain.toggleEnable

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-toggleEnable"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainIdYes

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 and idempotentHint but say nothing about destructiveness or read-only status, so the description carries the burden for whether this disables a live domain. It adds nothing: it does not say whether toggling is reversible, what permissions are required, or what state the domain ends up in. Worse, describing it as 'toggle' sits awkwardly beside idempotentHint=true, since a true toggle would not be idempotent — the agent gets no help resolving that ambiguity.

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 shortness comes from under-specification rather than efficiency. A bare HTTP route is not a front-loaded explanation of purpose, so brevity here earns nothing.

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, no annotation coverage of safety semantics, an undocumented required parameter, and a mutation that could take a domain offline, the definition is wholly inadequate. An agent has no basis to call this correctly or safely.

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?

The single required parameter domainId has 0% schema description coverage, so the description must explain it. It supplies no information about the parameter's format, where the ID comes from, or how it identifies the domain, leaving the agent to guess.

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.toggleEnable', which essentially restates the tool name. It implies a mutation on a domain entity and the verb 'toggleEnable' hints at an enable/disable state change, but it never states what is being enabled or what the tool actually does, and it does not distinguish this from siblings such as patch-toggleEnabled or gitProvider-toggleShare.

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, when-not-to-use, or prerequisite guidance of any kind. The agent must infer from the name alone that this flips a domain's enabled state, with no hint about alternatives for updating a domain (e.g. domain-update).

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