Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-changeStatus

Idempotent

Updates a MariaDB service's status in Dokploy by ID, setting it to idle, running, done, or error to reflect deployment state.

Instructions

POST /mariadb.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": {
      "mariadbId": "<mariadbId>",
      "applicationStatus": "<applicationStatus>"
    },
    "name": "mariadb-changeStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
mariadbIdYes
applicationStatusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the agent knows repeated calls are safe and that the tool touches external state. The description adds nothing: it does not say whether the status change is a declaration only, whether it restarts the container, or what permissions are needed. A raw route path carries no behavioral context for a mutation tool.

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 one route fragment with no wasted words, but that is under-specification rather than conciseness. There is no front-loaded statement of purpose for the agent 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 mutation tool with two required, fully undocumented parameters, no output schema, and only two weak annotations, the description supplies essentially none of the missing information. An agent cannot confidently call this correctly from the definition alone.

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%, so the description must carry the burden and it does not. mariadbId and applicationStatus are undocumented beyond the enum's literal values; the description gives no indication of whether mariadbId is a name, UUID, or ID-as-string, nor what each status transition implies.

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 just the HTTP route "POST /mariadb.changeStatus", which restates the tool name rather than explaining what the tool does. It does not say that it mutates a MariaDB instance's lifecycle status, nor what moving to a status like "error" or "done" actually means operationally.

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 guidance on when to use this versus the many overlapping siblings such as mariadb-start, mariadb-stop, mariadb-reload, or mariadb-update. An agent must infer that this is a lower-level status-setter compared to the dedicated start/stop verbs, with no confirmation in the text.

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