Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-start

Idempotent

Starts a specified MariaDB database instance in Dokploy using its ID, restoring database availability for connected applications and deployments.

Instructions

POST /mariadb.start

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-start"
  }
}

Input Schema

NameRequiredDescriptionDefault
mariadbIdYes

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 supply idempotentHint=true and openWorldHint=true, but the description adds zero behavioral context: nothing about whether the call is asynchronous, what happens when the instance is already running, expected latency, or whether the operation is reversible. For a state-changing lifecycle endpoint, the description carries a burden it completely fails to meet.

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?

There is no wasted wording, but that is because there is almost no content — a bare route string is under-specification rather than concision. It cannot be front-loaded because nothing substantive is stated.

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?

With no output schema, no annotation coverage of safety semantics, and 0% parameter documentation, the description would need to explain state-transition behavior and the identifier's origin. It supplies none of it, leaving the agent unable to call the tool confidently.

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% and there is one required parameter (mariadbId) with no documented format, sourcing, or meaning. The description mentions no parameters at all, so it fails to compensate for the documentation gap.

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.start" restates the tool name as an HTTP route; it conveys no verb-plus-resource phrasing beyond what the identifier already tells the agent. It never says what "start" means operationally (boot a stopped instance? restart?) or how it differs from mariadb-reload, mariadb-rebuild, or mariadb-changeStatus.

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, no prerequisites, no exclusions, and no pointer to alternatives such as mariadb-stop or mariadb-reload. The agent must infer the entire decision rule from the tool 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