Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-reload

Idempotent

Reload a MariaDB service in Dokploy to apply updated configuration for a specified application without redeploying the full stack.

Instructions

POST /mariadb.reload

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>",
      "appName": "<appName>"
    },
    "name": "mariadb-reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNameYes
mariadbIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations declare idempotentHint=true and openWorldHint=true but omit readOnlyHint and destructiveHint, so the description would need to clarify impact on connections, downtime, or config re-reads — it says nothing. The only new information is the implied POST mutation, which is minimal and already inferable from the name.

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 this is under-specification rather than conciseness: a bare route string with no front-loaded purpose statement, no body, and no structure to guide invocation.

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 mutating tool with two required undocumented parameters, no output schema, and annotations that omit destructive/read-only hints, the definition provides essentially nothing an agent needs to call it safely or 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?

Two required parameters (mariadbId, appName) have 0% schema description coverage and the description adds no meaning whatsoever about them. Nothing explains whether appName is a project/environment scope or how mariadbId is formatted, leaving an agent unable to populate required inputs confidently.

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 the endpoint label "POST /mariadb.reload", which merely restates the tool name in HTTP form. It signals a mutation-style reload of a MariaDB instance but adds no verb/resource explanation beyond what the name already implies, and gives no differentiation from siblings like mariadb-start or mariadb-rebuild.

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 at all: no mention of preconditions (e.g., the instance must be running), no distinction from restart/reload siblings, and no exclusions. An agent must guess between mariadb-reload, mariadb-start, and mariadb-rebuild purely from names.

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