Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Get application

coolify_get_application
Read-only

Retrieve details for a specific Coolify application by UUID and site to inspect its configuration, status, and related metadata.

Instructions

[UNIFIED] Get details of a specific Coolify application by UUID.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.7/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, so the bar is lower, yet the description adds nothing beyond that: no mention of authentication against a Coolify instance, what happens when the UUID is unknown, or what 'details' actually encompasses. The only added information is the UUID lookup key, which is really parameter semantics.

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?

One short sentence, front-loaded and free of padding. The only wasted token is the unexplained '[UNIFIED]' tag, and the sentence is arguably too terse rather than overly verbose.

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?

With no output schema, no parameter descriptions, and only a readOnly annotation, the description should explain the lookup key, the site parameter, and roughly what 'details' returns. It covers only the UUID angle, leaving an agent guessing about the second required parameter and the response shape.

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% for two required parameters, so the description must compensate and does not. It hints that 'uuid' identifies the application, but says nothing about 'site' (presumably the Coolify instance/target) or expected formats for either value.

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 gives a specific verb+resource: get details of a Coolify application, keyed by UUID. It is clear what the tool returns at a high level, but it does nothing to distinguish itself from siblings such as coolify_get_application_logs or coolify_get_database, and the '[UNIFIED]' prefix carries no explained meaning.

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 exclusions or alternatives mentioned. The phrase 'by UUID' weakly implies the identifier requirement, but an agent gets no help choosing this over the logs or list-style siblings.

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