Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-isolatedDeployment

Idempotent

Creates an isolated deployment for a Docker Compose service by compose ID, with an optional suffix to distinguish the deployment.

Instructions

POST /compose.isolatedDeployment

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

Input Schema

NameRequiredDescriptionDefault
suffixNo
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 declare openWorldHint=true and idempotentHint=true, but the description adds zero behavioral context: not what gets deployed, whether a build/queue entry is created, what permissions are needed, or how it interacts with the associated deployment-* tools. A scheduling/queueing mutation like this needs far more disclosure.

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 technically one line with no waste, but that is under-specification rather than conciseness; the single token string conveys an endpoint path rather than a front-loaded statement of purpose. Nothing an agent could act on is presented.

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?

With no output schema, two undocumented parameters, and a deployment-triggering side effect, the definition should explain what is created and what the caller receives back. None of that is present, so the definition is not adequate for calling this tool 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?

Schema description coverage is 0% for both parameters, so the description carries the full burden of explaining composeId and especially the optional suffix — and it explains neither. The meaning, format, and effect of "suffix" on the isolated deployment name are entirely undocumented anywhere in the definition.

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?

"POST /compose.isolatedDeployment" restates the tool name plus an HTTP verb and never says what the operation actually does. The agent is left to infer from the name that an isolated deployment of a compose stack is created, but the description supplies no object or effect beyond that.

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 and no mention of any alternative, despite siblings like compose-deploy, compose-deployTemplate, compose-cancelDeployment, and previewDeployment-* that plausibly overlap. Nothing indicates what distinguishes an "isolated" deployment from a normal compose deployment.

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