Skip to main content
Glama
Sign In
coolify-mcp

coolify-mcp

by frndchagas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Start/stop/restart database

controlDatabase
Destructive

Start, stop, or restart any database by UUID to manage its runtime state.

Instructions

Start, stop, or restart a database 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>",
      "action": "<action>"
    },
    "name": "controlDatabase"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, indicating this is a mutating operation with potential side effects. The description does not add further behavioral details like downtime impact or async behavior, but it is consistent with 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?

The description is a single sentence that is direct and free of filler. It earns its place by conveying the core functionality without unnecessary detail.

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?

The tool is simple with only two parameters, and annotations provide safety hints. However, the description does not mention important context like whether operations are asynchronous, if there are prerequisites (e.g., database must exist), or what response to expect, leaving gaps for an agent.

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

Parameters2/5

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

With 0% schema description coverage, the description should compensate for parameter meaning, but it only mentions 'by UUID' and relies on the schema's enum for action. It does not explain UUID format or the semantics of each action beyond their names.

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's function: start, stop, or restart a database by UUID. It uses specific verbs and names the resource, distinguishing itself from sibling tools that target applications or services.

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 basic context for when to use the tool (to control a database lifecycle) and identifies the required identifier (UUID). However, it does not explicitly mention alternatives or exclusions, such as why you might use controlService or startApplication instead.

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