Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-randomizeCompose

Idempotent

Randomizes a Dokploy compose deployment by ID, optionally appending a custom suffix to the generated name.

Instructions

POST /compose.randomizeCompose

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

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 supply openWorldHint=true and idempotentHint=true, but the description adds no behavioral context whatsoever: it does not say whether randomization mutates the deployed state, whether it destroys existing service definitions, whether a redeploy is required afterward, or how it interacts with the compose's running deployment. A mutation endpoint with only one annotation sentence and a bare route path leaves the agent guessing.

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 not concise in the useful sense: it is under-specified rather than economical. A single route string is front-loaded only trivially, and nothing in it earns a place as guidance 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 a mutating tool with an openWorld hint, no output schema, and two undocumented parameters, the description is wholly inadequate. An agent has no basis to decide when to call it, what 'suffix' means, or what side effects to expect.

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 parameters, so the description must compensate and does not. The required composeId and the optional 'suffix' parameter are completely unexplained — in particular, what 'suffix' randomizes or appends is entirely opaque and cannot be inferred from the name or type.

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 HTTP route "POST /compose.randomizeCompose", which restates the tool name rather than explaining what randomizing a compose does (regenerating IDs? shuffling service names? re-rolling secrets?). The verb+resource is at least identifiable from the name itself, but the description contributes no distinguishing detail versus siblings like compose-redeploy or compose-create.

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?

No when-to-use, when-not-to-use, or alternative guidance of any kind. An agent cannot tell from this text under what circumstances randomizing is appropriate versus redeploying, updating, or recreating the compose.

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