Skip to main content
Glama
MCP Dokploy Online
by igoruam

mariadb-remove

Destructive

Removes a MariaDB database instance from Dokploy using its ID to clean up unused database services.

Instructions

POST /mariadb.remove

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-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
mariadbIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered structurally, but the description adds nothing beyond that: no statement of what data is destroyed, whether removal is reversible, or whether dependent services must be stopped first. It does not contradict the annotations, but for a destructive endpoint it contributes no behavioral context.

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?

It is short but not front-loaded with anything useful; the single fragment is an endpoint path, which is under-specification rather than economy. Nothing in it earns a place as guidance for the caller.

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 an irreversible removal operation with a required identifier, zero schema description coverage, and no output schema, the definition provides no scope, preconditions, side effects, or failure behavior. It is wholly inadequate to call this tool safely.

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% and the single required parameter mariadbId is documented nowhere. The description gives no meaning, format, or source for that identifier, so an agent gets only what the self-describing property name 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 only "POST /mariadb.remove", which restates the tool name and the HTTP verb/path rather than explaining what is being removed or under what conditions. It does imply a destructive operation on a MariaDB resource, but adds no verb-plus-resource specificity 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 alternatives such as mariadb-stop, mariadb-changeStatus, or backup-remove. An agent must infer entirely from the name whether removal is the desired action.

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