Skip to main content
Glama
Sign In
coolify-mcp

coolify-mcp

by frndchagas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get database

getDatabase
Read-only

Retrieve complete database details by UUID to inspect configuration or troubleshoot issues, with optional secret values.

Instructions

Get database details 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": {
      "uuid": "<uuid>"
    },
    "name": "getDatabase"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes
showSecretsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, but the description adds no additional behavioral context beyond that. It does not disclose the effect of showSecrets (e.g., exposing sensitive values), any auth requirements, or limitations (e.g., not returning full configuration without the flag). This leaves important behavioral nuance unexplained.

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, front-loaded sentence with no filler. It wastes no words and is easy to parse, achieving maximum conciseness even if it is somewhat sparse.

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 and a minimal description, the agent cannot infer what 'details' are actually returned, how showSecrets changes the result, or how to find the correct UUID. For a tool with an optional flag that could expose sensitive data, this lack of context makes the description incomplete.

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 the purpose of the uuid parameter ('by UUID') but says nothing about showSecrets, leaving the boolean's meaning and effect ambiguous. The parameter names alone are insufficient for a confident invocation.

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?

Description clearly states the specific verb 'Get' plus resource 'database details' and identifier 'UUID'. This makes the tool's purpose unambiguous and distinct from siblings like listDatabases (which lists all databases) and createDatabase (which creates one).

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 provided on when to use this tool versus alternatives. For example, it does not mention that listDatabases should be used to discover UUIDs first, or that databaseEnvs/databaseBackups provide related but different data. There is no mention of exclusions or prerequisite steps.

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