Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-import

Idempotent

Import a Docker Compose configuration into an existing Dokploy compose service by supplying the compose ID and base64-encoded file.

Instructions

POST /compose.import

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": {
      "base64": "<base64>",
      "composeId": "<composeId>"
    },
    "name": "compose-import"
  }
}

Input Schema

NameRequiredDescriptionDefault
base64Yes
composeIdYes

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, but the description adds nothing beyond them. It does not disclose what the import creates or overwrites, whether existing composes are replaced, what permissions are required, or how failures are reported.

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 is under-specification rather than conciseness. The single line carries no information an agent could act on beyond the name itself.

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 import/mutation tool with two required undocumented parameters, no output schema, and only sparse annotations, the definition is far from complete. It lacks payload format, target semantics, and side-effect information.

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 two required parameters (base64, composeId), and the description compensates for none of it. An agent cannot tell from the definition what base64 encodes (a zip, a YAML, a tar?) or how composeId relates to the payload.

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 "POST /compose.import", which restates the tool name plus the HTTP method. It does not state what is being imported, from where, or what the outcome is, so it is essentially tautological rather than a specific verb-plus-resource statement.

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 whatsoever: no mention of prerequisites, no distinction from siblings like network-import, backup-manualBackupCompose, or compose-create, and no exclusion criteria.

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