Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-create

Create a MongoDB database instance in a Dokploy environment by providing a name, environment ID, and database credentials.

Instructions

POST /mongo.create

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": {
      "name": "<name>",
      "environmentId": "<environmentId>",
      "databaseUser": "<databaseUser>",
      "databasePassword": "<databasePassword>"
    },
    "name": "mongo-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
appNameNo
serverIdNo
descriptionNo
dockerImageNomongo:15
replicaSetsNo
databaseUserYes
environmentIdYes
databasePasswordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations give only openWorldHint=true, which conveys that the tool touches an external system but nothing about side effects or cost. The description carries the remaining burden and says nothing: no mention that it provisions a real database, that credentials are stored, whether the instance starts immediately, or whether the operation is reversible.

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 four-token fragment, so there is no bloat, but that is under-specification rather than conciseness. It is not front-loaded with purpose, prerequisites, or outcome, so there is nothing for an agent to anchor on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a resource-provisioning tool with nine parameters including database credentials and an external (openWorld) side effect, the definition supplies no behavioral or parameter context at all. It is far short of what an agent needs to call this safely and correctly.

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?

Nine parameters with 0% schema description coverage and four of them required, yet the description adds no meaning. Nothing explains the name vs appName distinction, the dockerImage default ("mongo:15"), replicaSets semantics, or the role of serverId/environmentId.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"POST /mongo.create" only restates the tool name in HTTP-route form. An agent can infer that a MongoDB resource is created, but there is no stated verb+resource scope, no mention of what is provisioned, and nothing to distinguish it from siblings like mongo-deploy or mariadb-create.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no when-to-use, when-not-to-use, prerequisites, or alternatives. There is no hint that this is the entry point before start/deploy/changePassword, leaving routing entirely to inference 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