Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-move

Idempotent

Moves a Docker Compose resource to a different target environment in Dokploy, letting you reorganize deployments between environments with a single API call.

Instructions

POST /compose.move

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>",
      "targetEnvironmentId": "<targetEnvironmentId>"
    },
    "name": "compose-move"
  }
}

Input Schema

NameRequiredDescriptionDefault
composeIdYes
targetEnvironmentIdYes

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 declare openWorldHint=true and idempotentHint=true, so the baseline bar is low, but the description adds nothing at all: it does not say what is moved, whether the source compose is deleted or left intact, what permissions are required, whether the deployment is stopped/restarted, or whether the move is reversible. The route string alone provides no behavioral context 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?

The text is extremely short but that is under-specification rather than conciseness; a bare route string earns no place as a tool description. There is no front-loaded statement of purpose or scope.

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 two-parameter mutation-style operation with no output schema and no annotation coverage of semantics, the description supplies none of the information an agent needs to invoke it safely or correctly. It is effectively an undocumented endpoint.

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 both required parameters (composeId, targetEnvironmentId), and the description does not compensate in any way — it does not say what a composeId identifies, what a targetEnvironmentId means, or whether the target must be empty/pre-existing. With low coverage the description carries the burden, and it fails entirely.

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.move", which restates the tool name rather than explaining the operation. It conveys only that the call is a POST (a mutation-ish action) against a compose resource; an agent cannot tell what 'move' does — relocate a compose to another environment, project, or host — or how it differs from siblings like application-move or compose-deploy.

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 many *-move siblings (application-move, mysql-move, postgres-move, etc.) exist but the description gives no hint about which resource type selects this tool or when moving is preferable to redeploying via compose-redeploy.

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