Skip to main content
Glama
Sign In
Coolify MCP Server

Coolify MCP Server

by kof70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

restart_service

Restart a service by providing its UUID. Requires confirmation when COOLIFY_REQUIRE_CONFIRM is set to true.

Instructions

Restart a service. When COOLIFY_REQUIRE_CONFIRM=true, requires confirm: true parameter.

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": "restart_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesService UUID
confirmNoConfirm the dangerous operation (required when COOLIFY_REQUIRE_CONFIRM=true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description must cover behavioral traits. It adds value by disclosing that an environment variable can require confirmation, which is a critical behavioral nuance. However, it does not explain other aspects like whether the restart is graceful or causes downtime.

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 extremely concise with two sentences: the first states the primary action, the second adds a conditional detail. No superfluous information, and the key purpose is front-loaded.

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

Completeness4/5

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

Given the simplicity of the tool (2 parameters, no output schema), the description adequately covers purpose and a key behavioral requirement. It could be slightly improved by noting expected effects (e.g., service restarts, potential downtime), but overall it is sufficiently complete.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds important context beyond the schema by explaining that confirm is required only when COOLIFY_REQUIRE_CONFIRM is set to true. This clarifies conditional usage beyond mere field types.

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

Purpose4/5

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

The description clearly states 'Restart a service' with a specific verb and resource. It distinguishes from siblings like start_service and stop_service by indicating a restart action, but does not explicitly differentiate from restart_application or restart_database.

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

Usage Guidelines3/5

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

The description provides a condition for the confirm parameter based on environment variable, but offers no guidance on when to use this tool versus other related tools (e.g., start_service, stop_service). Usage context is implied rather than explicit.

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