Skip to main content
Glama
Sign In
coolify-mcp

coolify-mcp

by frndchagas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List deployments

listDeployments
Read-only

Retrieve a paginated list of currently running deployments on your Coolify instance to monitor active processes.

Instructions

List currently running deployments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listDeployments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already cover the read-only safety profile via readOnlyHint and openWorldHint. The description adds the 'currently running' state filter, which is useful behavioral context, but it does not disclose pagination behavior, result ordering, or the implications of the openWorldHint flag.

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?

The description is a single, front-loaded sentence with no unnecessary words. It is concise and readable, though it sacrifices important detail; however, for its length it is well-structured.

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?

Given the tool's simplicity, the description is minimally viable, but it omits crucial details such as pagination, how results are scoped (e.g., across projects or apps), and how this differs from similar list tools. The annotations help with safety but not with invocation details.

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 schema contains two parameters, limit and offset, with no descriptions and 0% schema coverage. The description does not mention these parameters at all, so it fails to compensate for the lack of schema descriptions and provides no additional meaning.

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 clearly states the action (list) and resource (deployments) with a specific state qualifier ('currently running'). However, it does not differentiate this from the sibling tool listAppDeployments, which could also list deployments, so it doesn't fully distinguish among alternatives.

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?

The phrase 'currently running' gives some context for when to use this tool, but there is no explicit guidance on when to choose this over alternatives like listAppDeployments or getDeployment, and no mention of exclusions or prerequisites.

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