Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-stop

Idempotent

Stop a running MySQL database instance in Dokploy by its ID. Halts the service to free resources or pause access during maintenance.

Instructions

POST /mysql.stop

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>"
    },
    "name": "mysql-stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
mysqlIdYes

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 only openWorldHint=true and idempotentHint=true; nothing declares destructiveness, data persistence, connection termination, or required permissions. The description adds zero behavioral context, so for a state-changing lifecycle operation the burden is entirely unmet and the agent cannot tell if existing data or active connections are lost.

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 description is only a bare route string, so it wastes no words, but this is under-specification rather than conciseness. There is no front-loaded explanation of purpose or effect for the reader to anchor on.

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 lifecycle tool with no output schema and full annotation gaps around destructiveness, the definition should explain effects and prerequisites. Neither the description nor the structured fields cover them, so it is inadequate to call the tool safely.

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% for the single required parameter mysqlId, and the description says nothing about it. It does not clarify whether mysqlId is a service identifier, a database name, or an internal resource key, leaving the only input undocumented in both places.

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 only restates the tool name as an HTTP route ('POST /mysql.stop'), adding the transport method but no statement of what stopping means for the MySQL instance. An agent can guess that it halts a MySQL service, but the definition provides no verb-plus-resource explanation beyond the name itself.

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 how this differs from likely alternatives such as mysql-reload, mysql-remove, or mysql-changeStatus. The agent must infer 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