Skip to main content
Glama
0xtlt

coolify-mcp

by 0xtlt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

coolify_get_database_logs

Retrieve Coolify database logs and filter by log level, time range, or text search to quickly diagnose issues.

Instructions

Retrieve logs for a Coolify database with optional filtering by level, time range, or text search

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tailNoReturn the most recent logs (tail behavior)
uuidYesUUID of the database
levelNoMinimum log level to include
limitNoMaximum number of filtered log entries to return
linesNoServer log lines to fetch; all (or -1) fetches all. Defaults to limit. Filtering still caps the returned entries at limit.
sinceNoISO 8601 timestamp - only logs after this time
untilNoISO 8601 timestamp - only logs before this time
searchNoText to search for in log messages (case-insensitive)
show_timestampsNoInclude server timestamps for accurate time filtering

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.1.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of log entries to fetch from the server"New value: +"Maximum number of filtered log entries to return"
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / lines
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 10000,
+      "minimum": -1,
+      "type": "integer"
+    },
+    {
+      "const": "all",
+      "type": "string"
+    }
+  ],
+  "description": "Server log lines to fetch; all (or -1) fetches all. Defaults to limit. Filtering still caps the returned entries at limit."
+}
    • addedInput schema / properties / show_timestamps
      Added value: +{
+  "default": true,
+  "description": "Include server timestamps for accurate time filtering",
+  "type": "boolean"
+}
  2. First observedv4.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only conveys 'retrieve' (a read implication) and the filter options. It says nothing about pagination, whether logs are streamed or returned in a single batch, response size limits, or how tail/lines/limit interact — meaningful gaps for a logs tool.

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?

A single sentence of about 17 words, front-loaded with verb and resource, containing no fluff. The brevity is efficient, though it comes at the cost of missing usage and behavioral context captured in other dimensions.

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?

Given 9 parameters, no output schema, no annotations, and a crowded sibling set (coolify_get_logs, coolify_get_service_logs), the description is too thin. It omits return format, the behavior of tail/limit/lines, and any differentiation from the generic get_logs tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 9 parameters in detail. The description adds only a light grouping — 'level, time range, or text search' maps to level, since/until, and search — which is a minor semantic contribution. Baseline 3 applies.

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 uses a specific verb ('Retrieve') and resource ('logs for a Coolify database') and enumerates the filtering dimensions (level, time range, text search). It clearly identifies the resource type, which implicitly sets it apart from coolify_get_service_logs and coolify_get_application_preview_logs, but it does not explicitly contrast with the generic coolify_get_logs sibling.

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?

No guidance is given on when to choose this tool over siblings like coolify_get_logs or coolify_get_service_logs, and no prerequisites or exclusions are stated. The filtering clauses hint at contexts (e.g., debugging by level or time) but never make them explicit.

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