Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-deployTemplate

Idempotent

Deploy a Docker Compose template to a specified Dokploy environment and server using the template ID and environment ID to trigger the deployment.

Instructions

POST /compose.deployTemplate

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": {
      "environmentId": "<environmentId>",
      "id": "<id>"
    },
    "name": "compose-deployTemplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
baseUrlNo
serverIdNo
environmentIdYes

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 supply openWorldHint=true and idempotentHint=true, so the description owes context rather than repetition. Instead it discloses nothing about what gets created or mutated, whether the target environment must be empty, auth/permission requirements, or whether baseUrl/serverId override anything.

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 the brevity comes from under-specification rather than economy: a bare HTTP verb+path conveys almost nothing and is not front-loaded with any actionable intent. There is no sentence that earns its place.

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 four-parameter mutating deployment tool with no output schema and no descriptions anywhere in the schema, the definition is completely inadequate. An agent cannot tell what will be created, what the required id refers to, or what a successful response means.

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 (id, baseUrl, serverId, environmentId), and the description compensates with zero information. The meaning of id (template id? deployment id?) and the roles of baseUrl and serverId are entirely undocumented.

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.deployTemplate" only restates the tool name in HTTP-path form; it never says what deploying a template actually does (create a stack from a template, target an environment, etc.). It gives no way to distinguish it from siblings like compose-previewTemplate or compose-processTemplate, which the name alone implies are related operations.

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 at all: no mention of prerequisites, no contrast with previewTemplate/processTemplate/application-deploy, and no conditions under which this endpoint should be chosen. An agent must guess entirely from the name.

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