Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-reload

Idempotent

Reloads a specified MySQL instance for an application in Dokploy, applying configuration changes without recreating the database.

Instructions

POST /mysql.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": {
      "mysqlId": "<mysqlId>",
      "appName": "<appName>"
    },
    "name": "mysql-reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNameYes
mysqlIdYes

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?

Annotations already declare openWorldHint=true and idempotentHint=true, but the description adds nothing beyond them — no statement about what a reload does to running services, whether it causes downtime, whether auth is required, or what happens to active connections. The single path fragment carries zero behavioral content.

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?

The text is short, but its brevity reflects under-specification rather than efficiency; a bare route string is not a useful front-loaded summary. There is no wasted wording because there is essentially no content.

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 two required undocumented parameters, no output schema, and only sparse annotations, this definition leaves every operative question unanswered. An agent cannot safely invoke it without guessing at the meaning of mysqlId and appName.

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 both parameters (mysqlId, appName) are required, so the description bears full responsibility for explaining them. It says nothing — an agent cannot learn from the description whether mysqlId is an ID, slug, or name, or what appName scopes.

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 HTTP route "POST /mysql.reload", which restates the tool name rather than explaining what a reload does to a MySQL instance. There is no verb-plus-resource statement an agent could use to distinguish it from siblings like mariadb-reload or libsql-reload beyond the literal name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 mention of prerequisites, and no comparison to alternatives such as mysql-start, mysql-stop, or mysql-rebuild. The agent must infer reload semantics and selection criteria entirely from the name.

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