Skip to main content
Glama
MCP Dokploy Online
by igoruam

mysql-changeStatus

Idempotent

Update a MySQL service's application status in Dokploy to idle, running, done, or error by specifying its MySQL ID.

Instructions

POST /mysql.changeStatus

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

Input Schema

NameRequiredDescriptionDefault
mysqlIdYes
applicationStatusYes

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 already declare idempotentHint=true and openWorldHint=true, and the description neither contradicts nor enriches them. It does not state that this mutates a running instance's state, whether the change is disruptive, what the allowed transitions are, or how errors are reported — all of which matter for a 4-value status enum on a live database service.

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?

Extremely short, but short here means under-specified rather than efficient. The single route token is not front-loaded information an agent can act on; no sentence earns its place because there is effectively one.

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 two-required-parameter mutation tool with zero schema documentation and no output schema, the description should explain the resource, the status lifecycle, and the effect of the call. None of that is present, so an agent must guess at behavior entirely.

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 the description names no parameters, so the agent gets nothing about the semantics of mysqlId or applicationStatus (e.g. whether setting 'done' or 'error' has side effects, or whether transitions are validated). The enum in the schema is the only source of meaning.

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 /mysql.changeStatus", which restates the tool name plus an HTTP verb. It does not say what status is being changed (the schema hints at applicationStatus on a MySQL instance), nor how this differs from sibling tools like mariadb-changeStatus or mysql-update.

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 preconditions, and no named alternative. An agent cannot tell from this text whether it should call this instead of mysql-start, mysql-stop, or mysql-update.

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