Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-create

Creates a Docker Compose application in a Dokploy environment using a Git or raw compose file, enabling deployment of multi-container services.

Instructions

POST /compose.create

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

Input Schema

NameRequiredDescriptionDefault
nameYes
appNameNo
serverIdNo
sourceTypeNo
composeFileNo
composeTypeNo
descriptionNo
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 supply only openWorldHint=true, so the description carries the full behavioral burden and provides none. It does not disclose required permissions, side effects, whether creation triggers a build or deployment, or what the response contains. The HTTP verb hint is already implied by the name.

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 that brevity reflects under-specification rather than conciseness. An endpoint path is not a useful front-loaded summary of purpose for an agent.

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 an eight-parameter mutation tool with no output schema and near-zero annotation coverage, the description is entirely inadequate. An agent has no basis to select this tool over compose-import or to populate its parameters 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?

Eight parameters exist with 0% schema description coverage, so the description must compensate and instead says nothing. Key ambiguities are unaddressed: how sourceType interacts with composeFile/serverId, what composeType 'docker-compose' vs 'stack' means, and whether environmentId references an existing environment.

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 endpoint string "POST /compose.create", which restates the tool name rather than explaining what the tool does. It conveys a mutation via HTTP POST but never states what a 'compose' is here or what creation produces, so an agent cannot distinguish it from siblings like compose-import, compose-deployTemplate, or compose-update.

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. The agent is left to infer from the name alone whether this creates a compose from a template, a git source, or a raw file, versus calling compose-import.

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