Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-create

Create a MariaDB database in a specified Dokploy environment, configuring the database name, user, and password to provision a managed database for your application.

Instructions

POST /mariadb.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>",
      "databaseName": "<databaseName>",
      "databaseUser": "<databaseUser>",
      "databasePassword": "<databasePassword>"
    },
    "name": "mariadb-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
appNameNo
serverIdNo
descriptionNo
dockerImageNomariadb:6
databaseNameYes
databaseUserYes
environmentIdYes
databasePasswordYes
databaseRootPasswordNo

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?

The only annotations are title and openWorldHint, so the description carries the full behavioral burden and delivers nothing: no disclosure of side effects, whether credentials are stored or returned, what happens on name collision, or whether provisioning is synchronous or async.

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?

It is short, but brevity is achieved by omitting all substance; a bare REST route is not front-loaded information an agent can act on. The concision here reflects under-specification, not economy.

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 10-parameter creation tool with no output schema and near-empty annotations, the description is completely inadequate. An agent has no basis to choose this tool over sibling create tools or to fill the five required parameters 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?

All 10 parameters have 0% schema description coverage and the description adds zero meaning. The distinction between databasePassword and databaseRootPassword, the role of appName and serverId, and the default dockerImage value are all left entirely unexplained.

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 /mariadb.create" restates the tool name as an HTTP route. It implies creation of a MariaDB resource but says nothing about what is created (a server instance, a database, a user), how it relates to the required name/environmentId/databaseName fields, or what distinguishes it from siblings like mariadb-deploy or mariadb-update.

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?

No when-to-use guidance at all: no prerequisites, no mention of when a caller should create versus deploy, start, or rebuild, and no exclusions such as whether the target environment must already exist.

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