Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Validate server

coolify_validate_server
Destructive

Validate a Coolify server's connectivity and configuration, optionally installing prerequisites and restarting Docker to resolve setup issues.

Instructions

[UNIFIED] Validate server connectivity and configuration. With install=true, can also install prerequisites/Docker and restart the Docker daemon — mutating, so this tool requires write scope.

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_validate_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
uuidYes
installNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false and destructiveHint=true, and the description earns credit by specifying exactly what is destructive: installing prerequisites/Docker and restarting the Docker daemon. It also states the write-scope authorization requirement, which is context the annotations do not carry. It does not say what a failed validation looks like or whether the daemon restart is recoverable.

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

Conciseness4/5

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

Two tight sentences with the core purpose front-loaded and the mutation warning immediately after. The '[UNIFIED]' marker adds little and the sentence could be trimmed slightly, but nothing is wasted.

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 destructive, write-scoped tool with no output schema, the description covers the risk and the install behavior well. It stops short of describing what validation actually checks, what the response contains, or what site/uuid refer to, which an agent needs in order to call it correctly.

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?

Schema coverage is 0%, so the description must compensate, and it only explains one of three parameters — install=true installs prerequisites/Docker and restarts the daemon. The required 'site' and 'uuid' parameters are given no meaning anywhere, leaving the agent to guess their format.

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?

States a specific verb and resource: validate server connectivity and configuration. The '[UNIFIED]' prefix and the install flag distinguish it from plain read siblings like coolify_get_server, though the description never names an alternative explicitly.

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?

Implied usage is clear (check a server's connectivity/config), and it warns that install=true turns the call into a mutating operation. There is no explicit statement of when to prefer this over coolify_get_server or when not to call it at all.

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