coolify-mcp

Get application

getApplication

Read-only

Fetch application details by UUID from Coolify. Use optional field selection to request only the necessary data, reducing response size and avoiding irrelevant information.

Instructions

Get application details by UUID (optional field selection).

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": {
      "uuid": "<uuid>"
    },
    "name": "getApplication"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes
`fields`	No
`showSecrets`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description adds the behavior of optional field selection. However, it does not disclose behaviors around showSecrets or default response contents. With annotations covering the safety profile, this is adequate but not rich.

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

Conciseness5/5

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

A single sentence with no filler. Front-loads the verb and resource, and every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering read-only behavior and a relatively simple tool, the description is nearly complete. It could explain showSecrets or return details, but the core purpose is clear and the schema provides parameter types.

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%, so the description must compensate. It clarifies uuid as an identifier and mentions 'optional field selection' for the fields parameter, but showSecrets is entirely undocumented. Partial compensation is insufficient for three parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and resource ('application details') with a clear identifier ('by UUID'), distinguishing it from sibling tools like listApplications. The optional field selection is mentioned, adding further specificity.

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 description implies when to use the tool (when you have a UUID), but does not explicitly mention alternatives or exclusions. It gives some context but lacks direct guidance versus listing tools like listApplications.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server