Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-deploy

Idempotent

Deploy or update a Docker Compose stack in Dokploy by compose ID, optionally recreating volumes to support clean redeployments.

Instructions

POST /compose.deploy

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

Input Schema

NameRequiredDescriptionDefault
titleNo
composeIdYes
descriptionNo
freshVolumesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations declare idempotentHint=true and openWorldHint=true but say nothing about destructiveness, permissions, or side effects. The description adds nothing beyond the HTTP verb, and notably fails to warn that freshVolumes implies disposal of existing volume data.

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 economical. A bare endpoint path is not a useful front-loaded summary of 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, potentially destructive deploy operation with no output schema and zero-annotated parameters, the description provides nothing an agent needs to invoke it correctly.

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 four parameters, and the description supplies no semantics at all. The meaning of freshVolumes, title, and description — and what composeId refers to — is left entirely unexplained.

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?

"POST /compose.deploy" merely restates the tool name plus an HTTP method; it never says what deploying a compose resource actually does or what gets created. It does not distinguish this from siblings such as compose-deployTemplate, compose-isolatedDeployment, or the various database deploy tools.

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 mention of alternatives among the many deploy siblings. An agent has no basis for choosing this over compose-deployTemplate or compose-isolatedDeployment.

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