Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Restart database

coolify_restart_database
Destructive

Restart a Coolify database through MCP Hub to recover from connection issues, apply configuration changes, or restore service availability using the site and database UUID.

Instructions

[UNIFIED] Restart a Coolify database.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is known. The description adds nothing beyond that: no mention of downtime, dropped connections, whether data is preserved, or whether the call blocks until the database is back.

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

Conciseness3/5

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

It is a single short sentence, so it is not bloated, but the "[UNIFIED]" prefix is unexplained noise. Brevity here comes from omission rather than disciplined editing.

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

Completeness2/5

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

For a destructive mutation with no output schema, no parameter documentation, and no behavioral description, the definition is well short of what an agent needs to call it safely. The annotations carry the entire burden, and even they leave downtime and failure behavior unknown.

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 both required parameters (site, uuid), and the description supplies no meaning at all — it does not say whose uuid this is (database uuid vs. another identifier) or what format "site" takes. With zero compensating text, the parameters are entirely undocumented.

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

Purpose3/5

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

The description names a verb and resource ("Restart a Coolify database"), but it is essentially a restatement of the title and name, adding only an unexplained "[UNIFIED]" tag. It gives no differentiation from close siblings such as coolify_start_database, coolify_stop_database, or coolify_restart_application/service.

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?

There is no when-to-use guidance, no distinction between restart versus stop/start, and no mention of prerequisites or state requirements. The agent must infer everything about context from the name alone.

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