Skip to main content
Glama
MCP Dokploy Online
by igoruam

deployment-allByServer

Read-onlyIdempotent

Retrieve all Dokploy deployments for a specified server to inspect deployment history and status using its server ID.

Instructions

GET /deployment.allByServer

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": {
      "serverId": "<serverId>"
    },
    "name": "deployment-allByServer"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety is covered structurally. The description adds nothing beyond that — no indication of result shape, pagination, volume, or whether a missing server yields an empty list or an error.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is as short as possible with no wasted sentences, but this brevity comes from under-specification rather than disciplined editing. There is no front-loaded statement of purpose — only a machine-style path.

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 tool requiring a filter parameter with zero schema coverage and no output schema, the description should carry the full load. Instead it provides nothing about the parameter, return values, or behavior, leaving an agent unable to invoke it confidently.

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?

Schema description coverage is 0% for the single required parameter serverId, and the description supplies no compensating meaning. It never says serverId is the server to scope deployments to, nor what format/identifier type it accepts.

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 endpoint string "GET /deployment.allByServer", which restates the tool name rather than explaining what the tool does. An agent can infer it lists deployments filtered by server, but nothing states that explicitly or distinguishes it from siblings like deployment-allByCompose 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 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 prerequisites, and no indication of how this differs from the many sibling 'allBy*' deployment tools. The HTTP verb/path alone does not tell an agent when to choose this over deployment-all or deployment-allByType.

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