Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: List projects

coolify_list_projects
Read-only

Lists all Coolify projects for a specified site, so you can review available projects and select the right one.

Instructions

[UNIFIED] List all Coolify projects.

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

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.6/5.0
Behavior2/5

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

The readOnlyHint annotation already covers the safety profile, so the description only needed to add context beyond that, and it adds none: no pagination behavior, no indication of result size, and no explanation of the required 'site' input. Given a required parameter whose behavior is completely undisclosed, the description leaves the agent guessing about a key behavioral constraint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with nothing wasted, so it is concise, but the '[UNIFIED]' tag adds unexplained noise without conveying information. Brevity here is under-specification rather than tight writing.

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 parameter and no output schema, the definition is too thin. Missing are the meaning of 'site', the shape of the returned project list, and how it differs from sibling project-listing tools.

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?

There is one required parameter, 'site', with 0% schema description coverage, and the description never mentions it. With low coverage the description must compensate, but it provides no meaning, format, or example for the only parameter — an agent cannot know what value to supply.

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 Coolify projects. It is clear what the tool returns at a category level, but it does nothing to distinguish itself from the similarly named siblings such as list_projects, n8n_list_projects, or coolify_list_applications, and the '[UNIFIED]' prefix is unexplained.

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 guidance on when to use this tool rather than a sibling listing tool, nor any stated prerequisites such as authentication or a required project scope. The agent must infer usage purely from the name.

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