Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-redeploy

Idempotent

Redeploy a Docker Compose stack in Dokploy by compose ID, optionally recreating its volumes to apply updated configuration or recover from deployment issues.

Instructions

POST /compose.redeploy

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

Input Schema

NameRequiredDescriptionDefault
titleNo
composeIdYes
descriptionNo
freshVolumesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the description was not required to carry the full burden, yet it adds nothing at all beyond the route. It does not say what a redeploy replaces, whether existing containers or volumes are destroyed, how the freshVolumes parameter changes destructive behavior, or what the call returns.

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 not concise in any useful sense; it is under-specified rather than economical. A single route string gives the reader no front-loaded statement of purpose or behavior.

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 mutating redeploy operation with four undocumented parameters, no output schema, and only sparse annotations, the definition is far from complete. An agent has no basis to call this correctly or to reason about the consequences of the freshVolumes flag.

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% across four parameters, so the description is the only place meaning could be supplied, and it supplies none. The required composeId, plus title, description, and freshVolumes, are left entirely unexplained — especially freshVolumes, whose effect on data retention is critical and non-obvious.

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 HTTP route string "POST /compose.redeploy", which merely restates the tool name as an endpoint. It conveys that some redeploy action happens against a compose resource but never states what a redeploy means here, what it operates on, or how it differs from siblings such as compose-deploy or application-redeploy.

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 mention of alternatives. An agent cannot tell from this definition whether to call compose-redeploy versus compose-deploy, application-redeploy, or previewDeployment-redeploy.

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