Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-stop

Idempotent

Stops a specified MariaDB database instance in Dokploy by its ID, allowing you to halt the service when it is no longer needed.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
mariadbIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations only declare idempotentHint=true and openWorldHint=true; they say nothing about data persistence, graceful shutdown, downtime, or recovery. The description adds zero context about what stopping actually does to the instance or running connections.

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 not concise — it is under-specified, providing a bare route string with no front-loaded purpose statement. There is no structure an agent can use for decision-making.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a state-changing service operation with an undocumented required identifier and no output schema, so the description should carry substantial weight. It carries essentially none, leaving behavior, safety, and return expectations entirely unstated.

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?

There is one required parameter, mariadbId, with 0% schema description coverage, and the description says nothing about it. An agent must guess whether it is an instance ID, a container name, or a database name.

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.stop', which restates the tool name and path rather than stating an action. An agent can infer 'stops a MariaDB instance' only by decoding the route suffix, and nothing distinguishes it from siblings like mariadb-start or mysql-stop.

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?

No guidance is given about when to stop an instance versus restarting, reloading, or removing it, and no preconditions or consequences are mentioned. The sibling set contains mariadb-reload, mariadb-rebuild, and mariadb-remove, so the absence of any routing hint is a real gap.

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