Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-rebuild

Idempotent

Rebuild a MariaDB database service by its ID through the Dokploy API, recreating the container to apply configuration changes or recover from a failed state.

Instructions

POST /mariadb.rebuild

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

Input Schema

NameRequiredDescriptionDefault
mariadbIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations declare openWorldHint and idempotentHint but say nothing about destructiveness, yet a "rebuild" typically implies data or container replacement. The description adds no context on data loss risk, downtime, permissions, or reversibility, so it fails to carry the burden the annotations leave open.

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 brief, but the brevity comes from under-specification rather than economy; a bare endpoint string gives the agent no front-loaded purpose or structure to work with.

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 mutation-style operation with a required parameter, no output schema, and annotations that omit destructiveHint, the description should explain impact and prerequisites but supplies none of it.

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?

Schema description coverage is 0% for the single required parameter mariadbId, and the description provides no explanation of what identifier is expected (instance ID vs name) or where to obtain it. The name is semi-self-explanatory, but no meaning is added beyond the schema.

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 "POST /mariadb.rebuild", which restates the tool name and HTTP verb without saying what a rebuild actually does (redeploy container? reinitialize data directory? restart with new config?). An agent cannot distinguish the outcome from siblings like mariadb-reload or mariadb-deploy based on this text.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as mariadb-reload, mariadb-start, or mariadb-stop. The agent is left to infer everything 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