Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-deploy

Idempotent

Deploy a MariaDB database instance in Dokploy using its mariadbId to provision managed database infrastructure.

Instructions

POST /mariadb.deploy

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": {
      "mariadbId": "<mariadbId>"
    },
    "name": "mariadb-deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
mariadbIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

The annotations already declare openWorldHint and idempotentHint; the description adds nothing beyond them. No mention of what deploy mutates, whether it wipes existing data, what permissions are required, or how long it takes — significant gaps for an operation that clearly changes state.

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 the brevity is under-specification rather than efficiency — a bare HTTP verb plus path conveys no front-loaded purpose or constraints to an agent.

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 state-changing deploy operation with one undocumented parameter, no output schema, and only generic annotations, the definition is far too thin to call correctly or safely.

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?

There is a single required parameter, mariadbId, with 0% schema description coverage, so the description bears the full burden and contributes nothing. The meaning of the id is only guessable from its name; no format or source (e.g., from mariadb-search) is given.

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?

The description is only the endpoint string "POST /mariadb.deploy". It implies a deploy action targeted at a MariaDB instance, which loosely distinguishes it from mariadb-start/mariadb-stop, but it never states in prose what the tool does or what deploying entails.

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?

There is no guidance on when to use this over siblings such as mariadb-create, mariadb-rebuild, or mariadb-start, nor any prerequisites or exclusions. The agent must infer everything from the name alone.

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