Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-cleanAllDeploymentQueue

Idempotent

Clears all pending and queued deployment jobs in Dokploy settings, helping reset a stuck or unwanted deployment queue.

Instructions

POST /settings.cleanAllDeploymentQueue

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

Annotations only declare openWorldHint and idempotentHint; there is no destructiveHint and the description does nothing to fill that gap. A 'clean all' queue operation is plausibly destructive and irreversible, yet the description says nothing about what is removed, whether running deployments are affected, or what permissions are needed.

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 shortness here is under-specification rather than conciseness: the single line is a routing artifact with no front-loaded statement of purpose or effect.

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 bulk, likely-destructive queue cleanup exposed alongside queue-list and per-queue cleanup siblings, with no output schema and no destructiveHint, the description should carry the full disclosure burden and carries none of it.

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

Parameters4/5

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

The tool takes zero parameters, so the empty schema is fully self-documenting and there is no parameter semantics for the description to add. Baseline 4 applies.

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 /settings.cleanAllDeploymentQueue', which restates the tool name rather than describing the action in plain terms. An agent can infer a bulk cleanup of the deployment queue, but nothing states what 'clean' means (remove pending jobs? clear history? cancel running deployments?) or its scope.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives among the many siblings (deployment-queueList, settings-cleanAll, application-cleanQueues, compose-cleanQueues, deployment-killProcess). The agent has no basis for choosing this tool over the related cleanup tools.

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