Skip to main content
Glama
MCP Dokploy Online
by igoruam

deployment-allCentralized

Read-onlyIdempotent

Retrieves all centralized deployments from Dokploy so you can inspect deployment status and coordinate rollout visibility across projects.

Instructions

GET /deployment.allCentralized

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-allCentralized"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 covered without the description. The description adds nothing beyond that — no scope, no volume expectations, no note on what 'centralized' aggregation implies, and no rate or auth context.

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 reflects under-specification rather than efficiency — a single raw route string with no explanatory content. Nothing is wasted because nothing meaningful is present.

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 a crowded set of similarly named deployment siblings, the description is the only place where the distinction could be made, and it provides none. An agent cannot confidently choose this tool over deployment-all or the ByCompose/ByServer/ByType variants.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The empty schema with additionalProperties:false is self-explanatory.

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 only echoes the raw endpoint 'GET /deployment.allCentralized', which largely restates the tool name. The HTTP verb signals a read, but 'allCentralized' is never explained, so an agent cannot tell what this returns or how it differs from the adjacent 'deployment-all' sibling.

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 prerequisites, and no mention of alternatives such as deployment-all, deployment-allByCompose, or deployment-allByServer. The agent must guess the selection criteria from the name alone.

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