Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-stop

Idempotent

Stops a specified Docker Compose application in Dokploy using its compose ID, halting its running services.

Instructions

POST /compose.stop

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

Input Schema

NameRequiredDescriptionDefault
composeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare openWorldHint=true and idempotentHint=true; the description adds no behavioral context whatsoever, such as whether running containers are gracefully shut down, what happens to in-flight deployments, or whether the operation is reversible. No destructiveHint is present, so the description carries full burden for disclosing impact and does nothing.

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?

Brief, but this is under-specification rather than economy: the entire text is a route string with no front-loaded statement of purpose or effect. There is nothing to trim because nothing was said.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation with no output schema, the definition is too thin: it omits what stopping entails and what is returned or reported. An agent could still call it given the required composeId, but cannot predict consequences.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required composeId parameter, and the description supplies no meaning, format, or sourcing hint (e.g., name vs. ID, where to obtain it). Only the parameter's name conveys intent.

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.stop', which restates the tool name compose-stop rather than describing what stopping a compose actually does (halt running services? preserve containers? leave state?). It conveys the verb and resource only by implication from the identifier.

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 guidance on when to use this instead of alternatives such as compose-cancelDeployment, compose-delete, compose-killBuild, or compose-cleanQueues, and no stated prerequisites or exclusions. An agent must guess from sibling names alone.

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