coolify-mcp

Diagnose server

diagnoseServer

Read-only

Diagnose any server by UUID, name, or IP to list running resources, status breakdown, configured domains, and suggested next actions.

Instructions

Diagnose a server by UUID, name, or IP: lists the resources running on it with a status breakdown, configured domains, and suggested next actions.

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": {
      "identifier": "<identifier>"
    },
    "name": "diagnoseServer"
  }
}

Input Schema

Name	Required	Description	Default
`identifier`	Yes	Server UUID, name, or IP

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.5Aug 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds meaningful context by specifying that it aggregates resource status, domains, and suggested next actions, which goes beyond a simple read operation. No contradiction with 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, well-structured sentence that front-loads the verb and resource, then uses a colon to list the tool's outputs. Every word contributes value, and it is neither verbose nor under-specified.

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?

With one parameter, read-only annotations, and no output schema, the description provides a reasonable overview of what the tool returns. However, it could be more complete by detailing the format of the status breakdown or the nature of the suggested next actions, and any practical constraints like server connectivity.

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

Parameters3/5

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

The input schema already describes the single parameter as 'Server UUID, name, or IP' with 100% coverage. The description only restates this format without adding additional detail, so the baseline score of 3 is appropriate.

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 uses a specific verb ('diagnose') and resource ('server'), and clearly enumerates what it returns: running resources with status breakdown, configured domains, and suggested next actions. This distinguishes it from sibling tools like getServer, getServerResources, and getServerDomains.

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?

Usage context is implied through the diagnostic purpose and sibling tool names, but the description does not explicitly state when to use this tool versus alternatives such as getServer or getServerResources. No exclusions or alternative tool recommendations are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server