Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-killBuild

Idempotent

Terminates an active build for a specified application in Dokploy, stopping deployment processes when a build must be canceled.

Instructions

POST /application.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": {
      "applicationId": "<applicationId>"
    },
    "name": "application-killBuild"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the safety/idempotency profile is covered structurally. Beyond that, the description says nothing about the consequences of killing a build — whether artifacts, logs, or dependent deployments are affected, or what authorization is required. It does not contradict the annotations, but it adds zero behavioral context to a destructive-sounding mutation.

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 with no wasted words, but that brevity is under-specification rather than conciseness — a bare route string conveys no front-loaded intent an agent can act on beyond the HTTP method.

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

Completeness2/5

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

For a build-terminating mutation with no output schema and an undocumented parameter, the description should explain effect, target, and return behavior. Only the HTTP method is communicated; everything an agent needs to invoke this correctly and anticipate side effects is missing.

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?

There is one required parameter, applicationId, with 0% schema description coverage, and the description provides no information about it. The agent cannot tell whether it is a numeric ID, a slug, or whether it refers to the application owning the build rather than the build itself.

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 /application.killBuild" is essentially the tool name restated as an HTTP route. The verb "kill" and resource "build" are inferable from the name/path alone, so the description adds no distinguishing detail about what killing a build actually entails or how it differs from compose-killBuild or deployment-killProcess.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no exclusions. It does not say whether this targets a currently running build versus queued builds, or when to prefer compose-killBuild over this tool; the agent must guess from the name.

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