listServicesList all Coolify services, including one-click apps like databases and caches, with optional pagination and summary to manage your deployed resources.
List all Coolify services (one-click apps like databases, caches, etc.).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| summary | No |
Changes observed during successful MCP inspections.
v0.1.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the tool as readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds context about what constitutes a 'service' but does not disclose additional behavioral details such as pagination behavior or response structure. It does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that gets straight to the point. It is front-loaded with the verb and resource, and there is no unnecessary wording or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema and three undocumented parameters, yet the description only provides a one-line purpose. It does not explain what the response contains, how pagination works, or what the 'summary' flag does, leaving significant gaps for a list operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for explaining limit, offset, and summary. The description contains no mention of these parameters or what they control, leaving the agent without any semantic guidance beyond the raw schema types and constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the operation ('List') and the resource ('Coolify services') with examples ('one-click apps like databases, caches, etc.'). It is specific enough to distinguish from many sibling tools, though the examples could create ambiguity with listDatabases and listApplications since it doesn't explicitly state how services relate to those.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus alternatives like listApplications or listDatabases. It simply states 'List all Coolify services,' which implies usage only by the resource name but does not clarify scenarios or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.