Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-killBuild

Idempotent

Cancels an in-progress Docker Compose build using its compose ID, so stalled or unwanted deployments can be stopped and resources freed.

Instructions

POST /compose.killBuild

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

Input Schema

NameRequiredDescriptionDefault
composeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations declare idempotentHint=true and openWorldHint=true, but the description adds nothing beyond them – it doesn't say what state the build is left in, whether running deployments are affected, what permissions are needed, or what the response contains. For a destructive-sounding kill operation, this is a substantial gap and only the bare annotation hints give any behavioral signal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is certainly short, but that is under-specification rather than concision – a single raw route string with no front-loaded summary sentence. Nothing extraneous, but nothing informative either.

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?

No output schema and almost no annotations, so the description carries the full burden for a mutation-like operation with an undocumented identifier parameter. An agent cannot determine what the tool will do, what it affects, or what it returns.

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?

There is one required parameter, composeId, documented in the schema only as a constrained string with zero description coverage (0%). The description does not explain what composeId refers to or how to obtain it, so it adds no meaning beyond the schema shape.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is only the raw route string "POST /compose.killBuild". It restates the tool name as an HTTP endpoint and never says in plain language what the operation does (stop an in-progress build? cancel it? kill a build process?). An agent must infer the purpose from the endpoint name alone.

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 about when to use this tool versus siblings such as compose-cancelDeployment, compose-deploy, or application-killBuild. No prerequisites or conditions are stated, so selection between the many kill/cancel tools is left entirely to guesswork.

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