coolify-mcp

Restart application

restartApplication

Destructive

Restart a Coolify application by its UUID to apply changes or recover from failures.

Instructions

Restart an application by UUID.

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": {
      "uuid": "<uuid>"
    },
    "name": "restartApplication"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Aug 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already disclose that this is a mutating (readOnlyHint=false) and destructive (destructiveHint=true) operation. The description adds no extra behavioral context, such as expected downtime or order of operations, but it does not contradict the annotations either.

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

Conciseness5/5

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

The description is a single concise sentence: 'Restart an application by UUID.' It is front-loaded, contains no redundant words, and is suitably sized for the tool's simplicity.

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 simple operation with one parameter, the description is adequate but lacks important context such as prerequisites, side effects, or return behavior. Since no output schema exists and annotations are present, the description could have mentioned that restarting causes downtime or requires a running app, but it does not.

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

Parameters3/5

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

The input schema only defines 'uuid' as a required string with no description. The description's 'by UUID' clarifies that the parameter identifies the application, but adds minimal meaning beyond the tool name and schema. Since there is only one parameter and 0% schema coverage, the description partially compensates but does not specify format or constraints.

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

Purpose5/5

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

The description clearly states the tool restarts an application, using the specific verb 'restart' and specifying the resource ('application') and identifier ('by UUID'). It distinguishes from siblings like startApplication and stopApplication by naming the exact action, and from restartProjectApps by referring to a single application.

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 guidance is provided on when to use this tool versus alternatives such as restartProjectApps, or how it relates to startApplication/stopApplication. The description does not mention prerequisites (e.g., app must exist or be running) or contexts where it should be preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server