Skip to main content
Glama
MCP Dokploy Online
by igoruam

deployment-queueList

Read-onlyIdempotent

Fetch the Dokploy deployment queue to inspect pending and active deployment tasks and manage infrastructure workflows.

Instructions

GET /deployment.queueList

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": "deployment-queueList"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is fully covered by structured data; the endpoint string adds nothing on top. Nothing is said about ordering, whether the queue is live or historical, pagination, or what a queue entry represents — gaps that matter for a queue-reading tool.

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 brevity comes from under-specification rather than efficient writing; a raw route string is not a useful description. There is no wasted sentence because there is essentially no sentence.

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?

A tool positioned among ~20 deployment siblings, with no output schema, needs description text to explain what the queue is and when it is the right call. None of that exists, so an agent cannot confidently invoke this over the alternatives.

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 per the baseline this dimensions starts at a 4 and there is no parameter meaning the description could add or omit. Nothing in the schema is left undocumented.

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?

"GET /deployment.queueList" merely restates the tool name as an HTTP method plus path; the verb/resource is identical to what the identifier already conveys. It gives no indication of what the deployment queue actually contains or how it differs from siblings like deployment-all or deployment-allByServer.

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 guidance, no exclusions, and no reference to any alternative among the many deployment-* siblings. The agent is left to guess whether this returns pending items, historical items, or an aggregate view.

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