Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Get application logs

coolify_get_application_logs
Read-only

Retrieve Coolify application logs by site and UUID, with an optional line limit, to diagnose deployment or runtime issues.

Instructions

[UNIFIED] Get logs for a Coolify application.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
uuidYes
linesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.4/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 description's job is to add behavioral context beyond that — and it adds none. It does not say whether logs are live-streamed or historical, whether the call blocks, what happens if the application has no logs, or how large the response can get.

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?

A single sentence is appropriately compact and front-loads the verb, but the bracketed "[UNIFIED]" token is unexplained and the brevity comes at the cost of substance. It is concise without being informative.

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 no annotations beyond readOnlyHint, the description leaves the agent without the essentials: the shape of returned log lines, the meaning of the tail parameter, or any error/empty-log behavior. For a 3-parameter tool this is a significant gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must carry the burden and it does not. Nothing explains that "site" is the Coolify instance, that "uuid" identifies the target application, or what "lines" (default 100) means as a tail size.

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 states a specific verb and resource ("Get logs") scoped to a Coolify application, which is enough to separate it from siblings like coolify_get_application (metadata) or coolify_restart_application (lifecycle). The unexplained "[UNIFIED]" prefix adds noise rather than meaning, but the core purpose is unambiguous.

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 versus alternatives, no prerequisites (e.g., a deployed/running application, auth requirements), and no statement about what kind of logs are returned. The agent must infer usage entirely 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