Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-stop

Idempotent

Stops a running Dokploy application using its application ID, so you can halt a service or deployment when it should no longer be active.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

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 only declare idempotentHint=true and openWorldHint=true; the description adds no behavioral context whatsoever. It does not say whether the stop is graceful or forced, what happens to in-flight requests, whether the app must be running, or whether it can be undone — all of which matter for a mutation endpoint.

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 that is under-specification rather than conciseness; a bare HTTP route with no sentence structure. There is no front-loaded statement of purpose or consequence for the agent to act on.

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 destructive-by-nature lifecycle operation with no output schema, no parameter docs, and only two weak annotations, the definition is critically incomplete. An agent would have to guess at effects, failure modes, and return behavior before calling it.

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 the single required parameter applicationId, so the description must carry the load and it says nothing about the identifier's meaning or accepted form. No guidance on what value to supply or what happens with an invalid or unknown ID.

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 raw endpoint "POST /application.stop", which restates the tool name rather than explaining the operation. An agent can infer that it stops the named application, but nothing about scope, effect, or how it differs from sibling stop tools (compose-stop, docker-stopContainer, redis-stop) is conveyed.

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, no preconditions, and no mention of alternatives such as application-killBuild, application-cancelDeployment, or application-reload. The only context available is the sibling list, which is not the description's doing.

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