Skip to main content
Glama
MCP Dokploy Online
by igoruam

deployment-all

Read-onlyIdempotent

Retrieves all deployments for a specified application, letting users inspect deployment history and status through Dokploy.

Instructions

GET /deployment.all

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

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

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=true, idempotentHint=true, openWorldHint=true, so the safety profile is covered without the description. The description adds nothing beyond that — no indication of scope, pagination, ordering, or the shape of the returned deployment list.

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 only because it is under-specified rather than efficient; there is no front-loaded purpose statement or useful framing, just a raw endpoint string.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameter documentation, the description is the only source of semantic meaning, and it supplies none. For a one-parameter listing tool with many near-identical siblings, this leaves the agent unable to call it confidently or correctly.

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 required parameter applicationId, so the description must carry the burden of explaining its meaning. It says nothing about the parameter, leaving the agent to infer the scope from the name alone.

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 just "GET /deployment.all", a restatement of the tool name as an HTTP method and path. It does not say what a "deployment.all" actually is (a list of deployments scoped to an application?) or how it differs from siblings like deployment-allByCompose, deployment-allByServer, or deployment-allByType.

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 or when-not-to-use guidance, and no alternative is named. The agent cannot tell from the description whether this is the unfiltered/global listing or how it relates to the ByCompose/ByServer/ByType variants.

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