Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-cleanQueues

Idempotent

Clear pending queues for a specified Dokploy application by providing its applicationId, helping resolve stuck deployment or processing backlog.

Instructions

POST /application.cleanQueues

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": {
      "applicationId": "<applicationId>"
    },
    "name": "application-cleanQueues"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations only declare openWorldHint=true and idempotentHint=true; they say nothing about whether the call destroys in-flight jobs or running deploys. The description adds no behavioral context at all — no side effects, no authorization requirements, no reversibility — leaving the most consequential aspect of a queue-clearing mutation entirely undisclosed.

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 brevity here is under-specification rather than conciseness; a bare endpoint string is not a usable definition. Nothing is front-loaded because there is nothing substantive to front-load.

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 potentially destructive, open-world mutation with no output schema and sparse annotations, the description should explain scope and consequences, yet it contains none of that. An agent has no basis to call this safely.

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?

The single parameter applicationId has 0% schema description coverage, and the description provides no compensating meaning (no format, no example, no note on which application scope is affected). The description contributes nothing beyond the parameter's name.

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 raw route string "POST /application.cleanQueues", which restates the tool name rather than explaining the operation. It conveys the HTTP verb and the target resource name, but says nothing about what 'cleaning queues' actually does for an application.

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 guidance on when to invoke this versus the many cleanup siblings (settings-cleanAll, settings-cleanAllDeploymentQueue, compose-cleanQueues). No prerequisites, exclusions, or context are given, so an agent must guess.

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