coolify-mcp

Get server resources

getServerResources

Read-only

List all applications, databases, and services running on a server by providing its UUID. Get a clear overview to manage and monitor server resources.

Instructions

List all resources (applications, databases, services) running on a server.

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>"
    },
    "name": "getServerResources"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.5Aug 7, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to restate safety. It adds the specific resource types included (applications, databases, services), which is useful, but it does not disclose potential response size, pagination, or filtering behavior. The description is consistent with annotations; no contradiction.

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, clear sentence with no redundant phrasing. It efficiently conveys the tool's purpose and resource scope.

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 simple list tool with one parameter and no output schema, the description covers the core purpose but misses parameter semantics and usage guidance. The ambiguity with the sibling tool listResources further reduces completeness, making this a minimally viable description rather than a fully self-contained one.

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?

The input schema has one required parameter (uuid) with 0% description coverage. The description does not explain that uuid refers to the server identifier, leaving the agent to infer it from the tool name and resource context. This is a clear gap that the description should have compensated for.

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 'List all resources (applications, databases, services) running on a server' uses a specific verb and resource, clearly defining a consolidated resource listing scoped to a server. It distinguishes from getServer (server info) and from listApplications/listDatabases/listServices (singular resource types), though it may overlap with listResources.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies a server-scoped resource listing but does not mention when to prefer it over calling individual list tools or how it relates to listResources. No exclusions or alternative names are provided.

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

Deploy Server