Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-cleanQueues

Idempotent

Clears queued deployment jobs for a Dokploy compose service using its composeId, helping resolve pending or stuck queue entries.

Instructions

POST /compose.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": {
      "composeId": "<composeId>"
    },
    "name": "compose-cleanQueues"
  }
}

Input Schema

NameRequiredDescriptionDefault
composeIdYes

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 only supply openWorldHint=true and idempotentHint=true; they say nothing about what state is removed or whether the operation is destructive. The description adds no behavioral context at all — not what a 'queue' is here, whether in-flight deployments are affected, or what permissions are needed. It does not contradict the annotations, so no contradiction flag.

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 comes from under-specification rather than economy — the entire text is a method-and-path stub with no front-loaded explanation of the operation.

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 mutation-style endpoint with an undocumented required parameter and no output schema, the description provides nothing an agent needs: no effect, no side effects, no return shape. This is effectively an empty definition.

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 parameter composeId has 0% schema description coverage, and the description never mentions it. There is no indication of whether it identifies a compose project, a queue, or a deployment, so the description fails to compensate for the coverage gap.

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 "POST /compose.cleanQueues", which restates the tool name and HTTP path without saying what cleaning queues does (drop pending deployment/build jobs? purge failed queue entries?). An agent cannot distinguish the effect from siblings like compose-cancelDeployment, compose-clearDeployments, or settings-cleanAll.

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, no preconditions, and no routing to alternatives among the many other clean*/cancel* siblings. The HTTP verb plus path conveys no situational context.

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