Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-cleanAll

Idempotent

Clears all settings for a specified Dokploy server, removing its stored configuration data through the settings API endpoint.

Instructions

POST /settings.cleanAll

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "settings-cleanAll"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations declare openWorldHint=true and idempotentHint=true but say nothing about destructiveness, which is the key trait here. The description adds only the POST verb and gives no indication of what state is destroyed, whether the action is reversible, or what permissions are required for a broad "cleanAll" sweep.

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 economy – a bare endpoint string with no front-loaded statement of effect. Nothing in it is wasted, yet almost nothing useful is present.

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 destructive, open-world, scope-wide cleanup operation with an undocumented parameter and no output schema, the description supplies none of the needed context (target resources, scope of "All", irreversibility, auth). It is functionally insufficient to call the tool 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?

Schema description coverage is 0% for the single optional `serverId` parameter, and the description says nothing to compensate. An agent cannot tell whether omitting `serverId` means all servers (plausible given "All") or a default server, which is a meaningful ambiguity for a destructive operation.

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 string "POST /settings.cleanAll" – an HTTP method plus route restatement of the tool name. It signals a mutating settings operation but never says what is being cleaned (containers, images, keys, monitoring data?), so an agent cannot distinguish it from siblings like settings-cleanStoppedContainers or settings-cleanSSHPrivateKey without guessing.

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?

No when-to-use, when-not-to-use, or prerequisite information is provided. Because the sibling set contains roughly a dozen cleanup tools with overlapping scope, the absence of any routing guidance is a real gap rather than a minor one.

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