Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Get server

coolify_get_server
Read-only

Retrieve details and settings for a specific Coolify server using its UUID and site, so you can inspect configuration and status.

Instructions

[UNIFIED] Get details of a specific server by UUID, including settings.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.7/5.0
Behavior2/5

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

The readOnlyHint annotation already tells the agent this is a safe read, so the description's only added behavioral claim is 'including settings', which is too vague to act on. It says nothing about what 'settings' contains, whether secrets are redacted, or what happens when the UUID doesn't exist.

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?

A single front-loaded sentence with no filler beyond the opaque '[UNIFIED]' tag. It is appropriately sized, though the brevity comes at the cost of the missing parameter and usage detail noted elsewhere.

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 tool with a required, undocumented 'site' parameter, no output schema, and no annotations beyond readOnlyHint, the description is too thin. An agent knows it retrieves a server but not how to form a valid call beyond the UUID, nor what the response shape will be.

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 description coverage is 0% for both parameters, so the description must compensate and largely fails: it explains only that 'uuid' identifies the server, and never mentions the required 'site' parameter or what it represents (Coolify instance/base URL). One of two required parameters is left completely undefined.

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?

The description gives a specific verb+resource ('Get details of a specific server') and identifies the lookup key (UUID), which cleanly separates it from mutating siblings like coolify_create_server or coolify_delete_server. It doesn't explicitly distinguish itself from coolify_get_server_domains or coolify_get_server_resources, and the '[UNIFIED]' prefix is unexplained noise rather than scope information.

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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer from the name alone that this is the general-purpose server lookup while the domains/resources siblings are sub-views.

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