Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-update

Idempotent

Updates an existing Docker Compose service in Dokploy by ID, letting you change its compose file, environment variables, Git source, and deployment settings.

Instructions

POST /compose.update

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

Input Schema

NameRequiredDescriptionDefault
envNo
iconNo
nameNo
ownerNo
branchNo
suffixNo
appNameNo
commandNo
giteaIdNo
githubIdNo
gitlabIdNo
composeIdYes
createdAtNo
randomizeNo
autoDeployNo
giteaOwnerNo
repositoryNo
sourceTypeNo
watchPathsNo
bitbucketIdNo
composeFileNo
composePathNo
composeTypeNo
descriptionNo
giteaBranchNo
gitlabOwnerNo
triggerTypeNo
customGitUrlNo
gitlabBranchNo
refreshTokenNo
composeStatusNo
createEnvFileNo
environmentIdNo
bitbucketOwnerNo
bitbucketBranchNo
customGitBranchNo
giteaRepositoryNo
gitlabProjectIdNo
serviceNetworksNo
enableSubmodulesNo
gitlabRepositoryNo
customGitSSHKeyIdNo
isolatedDeploymentNo
bitbucketRepositoryNo
gitlabPathNamespaceNo
bitbucketRepositorySlugNo
isolatedDeploymentsVolumeNo

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 openWorldHint=true and idempotentHint=true, but the description adds no behavioral context at all — nothing about which fields are overwritten, whether omitted fields are cleared or preserved, permission requirements, or side effects on running deployments. For a 47-parameter mutation, the zero added context is a serious gap.

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 with no wasted words, but that brevity reflects under-specification rather than conciseness. A single route string cannot front-load useful information 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?

Given 47 parameters, one required field, no output schema, and no parameter documentation, the definition is wholly inadequate. An agent cannot determine what a valid update looks like or what happens to unspecified fields.

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 47 parameters, including non-obvious ones like suffix, randomize, isolatedDeploymentsVolume, watchPaths, triggerType, and serviceNetworks. The description provides no parameter meaning whatsoever, so it fails to compensate for the near-total absence of schema documentation.

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.update", which restates the tool name and implies an update of a compose resource. It adds no scope, no statement of what fields change, and no differentiation from siblings such as compose-create, compose-move, or compose-deploy. It is marginally more than a bare tautology but conveys nothing an agent couldn't get from the name.

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 the many adjacent siblings (compose-create for new resources, compose-deploy for deployment, compose-move for relocation). An agent must guess entirely from the tool name whether this is the correct call.

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