Skip to main content
Glama
Sign In
coolify-mcp

coolify-mcp

by frndchagas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Restart all project applications

restartProjectApps
Destructive

Restart all applications in a project, optionally limited to a specific environment. Confirmation prompt prevents accidental downtime.

Instructions

Restart every application in a project (optionally a single environment). Asks for confirmation on clients that support elicitation.

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": {
      "project_uuid": "<project_uuid>"
    },
    "name": "restartProjectApps"
  }
}

Input Schema

NameRequiredDescriptionDefault
environmentNoEnvironment name or UUID to restrict to
project_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag the tool as destructive and non-read-only. The description adds the confirmation prompt on supporting clients and emphasizes the broad scope ('every application'), providing extra behavioral context beyond the annotations.

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?

Two concise sentences, front-loaded with the main action and no unnecessary wording. The optional environment scope and confirmation behavior are mentioned in a compact manner.

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?

For a two-parameter action with no output schema, the description covers the action, scope, optional restriction, and confirmation behavior. It does not detail return values or error handling, but those are less critical for a restart operation.

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

Parameters4/5

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

The description clarifies both parameters: 'in a project' explains project_uuid, and 'optionally a single environment' explains the environment parameter. Since the schema only describes environment, the description compensates for the undocumented project_uuid.

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 every application in a project, optionally limited to a single environment. The verb 'Restart' plus the project-wide scope distinguishes it from the sibling restartApplication tool.

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

Usage Guidelines4/5

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

The description provides clear context by specifying 'every application in a project' and the optional 'single environment' restriction, implicitly indicating when this tool is appropriate. It does not explicitly mention alternatives, but the scope is self-explanatory.

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