Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-start

Idempotent

Starts a Dokploy Compose application by its ID so you can resume a stopped stack and bring its services online.

Instructions

POST /compose.start

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

Input Schema

NameRequiredDescriptionDefault
composeIdYes

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 already declare idempotentHint=true and openWorldHint=true, and the only behavioral signal in the description is the HTTP verb POST, which implies a state-changing call. The description does not say what state is created, whether the call blocks until containers run, what permissions are needed, or what happens if the compose is already running — so it adds essentially nothing beyond the annotations.

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 this is under-specification rather than conciseness — a bare route string with no front-loaded statement of purpose or effect. There is no structure to speak of.

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?

This is a state-changing lifecycle operation with no output schema, no schema descriptions, and no annotations covering safety (no readOnlyHint/destructiveHint), so the description carries the full burden and provides none of it. An agent cannot tell what starting a compose does, what it returns, or how failures surface.

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 composeId, and the description supplies no compensating meaning: no format, no source (existing compose ID vs. name), and no error behavior for an invalid or unknown ID.

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 just the HTTP route 'POST /compose.start', which restates the tool name rather than explaining what starting a compose actually does. An agent can guess it initiates a previously created compose definition, but nothing in the text confirms that, and it offers no distinction from siblings like compose-deploy, compose-create, or application-start.

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 (e.g. compose must exist / be created first), and no mention of any alternative such as compose-deploy for deployment versus compose-start for running. Nothing routes the agent to or away from this tool.

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