Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: List servers

coolify_list_servers
Read-only

Lists all servers registered in a Coolify instance for a specified site, so you can identify available infrastructure before managing deployments.

Instructions

[UNIFIED] List all servers registered in the Coolify instance.

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

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.8/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read. Beyond that, the description adds only that results are limited to the current Coolify instance; it says nothing about pagination, result ordering, or what a server record includes. The '[UNIFIED]' prefix is unexplained jargon that conveys no behavioral information.

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 short sentence with the resource front-loaded and no padding. The only waste is the unexplained '[UNIFIED]' tag, which adds a token but no meaning.

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 read-only list tool whose safety profile is fully covered by annotations and which has no output schema to explain, the core purpose is adequately conveyed. However, given a required but completely undocumented parameter, the definition leaves a real gap an agent would hit on the first call.

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 single required parameter 'site' has zero schema description coverage, and the description never mentions it at all. With only one parameter and no bundled schema text, the description carries the full burden of explaining what 'site' scopes or what value format it expects, and it does not.

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: list all servers registered in the Coolify instance. The distinction from siblings like coolify_list_applications or coolify_list_projects is implicit in the resource noun, so an agent can select it without opening the schema, though the description itself does not name a contrast.

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 prerequisites, and no mention of alternatives or when this tool should not be chosen. The only usage signal is the word 'all', which hints at an unfiltered enumeration but is never stated as guidance.

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