Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Create mongodb

coolify_create_mongodb
Destructive

Create a MongoDB database on Coolify with project, server, environment, and site details, and optionally deploy it immediately after creation.

Instructions

[UNIFIED] Create a MongoDB database on Coolify.

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>",
      "project_uuid": "<project_uuid>",
      "server_uuid": "<server_uuid>",
      "environment_name": "<environment_name>"
    },
    "name": "coolify_create_mongodb"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
siteYes
descriptionNo
server_uuidYes
project_uuidYes
instant_deployNo
environment_nameYes

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?

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so safety signaling is covered. The description adds nothing beyond that: it does not say that creation requires existing project/server/environment resources, what instant_deploy triggers, whether duplicate names are rejected, or what is returned.

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

Conciseness2/5

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

A single sentence with no filler, but this is under-specification rather than conciseness; the bracketed "[UNIFIED]" token is unexplained jargon that consumes space without informing the agent.

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?

For a mutation tool with 7 undocumented parameters, no output schema, and destructive semantics, the description is far too thin. An agent knows what resource is created but not the required preconditions, parameter meanings, or side effects, leaving real risk of incorrect invocation.

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 7 parameters, including ambiguous ones like site, instant_deploy, and environment_name, yet the description explains none of them. With the schema carrying no descriptions, the description must compensate and completely fails to do so.

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 names a specific verb (Create) and a specific resource (a MongoDB database on Coolify), which lets an agent distinguish it from siblings like coolify_create_postgresql or coolify_create_mysql by resource alone. The opaque "[UNIFIED]" prefix adds no meaning but does not obscure the core purpose.

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 the other database-creation siblings, and no mention of prerequisites such as an existing project, server, or environment, even though three of the four required parameters imply those must already exist. The agent must infer the entire workflow from the schema.

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